Ben Atkins 1a13748ab1 Attempt to sort based on primary key in scope methods on VersionConcern if primary key is an integer. ... This makes some of the changes to these scope methods that came from 6a4aba2 more flexible, in that the user can choose to compare timestamps if desired, but it defaults to comparing and sorting, via the primary key (if it is an integer). If the primary key is not an integer, it still defaults to using the PaperTrail.timestamp_field. This is my proposed fix for #314, and I also believe it should fix #317. It seems that that this issue is usually encountered when testing PaperTrail with MySQL (presumably due to lack of microsecond timestamp support).		2014-04-30 18:13:04 -04:00
..
frameworks	fix PaperTrail::Rails::Controller.included method	2014-04-02 14:27:59 -06:00
serializers	Upcasing the provided YAML and JSON serializers	2013-10-17 22:05:24 -04:00
cleaner.rb	Tests to cover changes from cb46e87; Cleaner module should group versions by PaperTrail.timestamp_field	2014-03-18 15:56:53 -04:00
config.rb	Upcasing the provided YAML and JSON serializers	2013-10-17 22:05:24 -04:00
has_paper_trail.rb	Attempt to sort based on primary key in scope methods on VersionConcern if primary key is an integer.	2014-04-30 18:13:04 -04:00
version.rb	Move VersionConcern module into it's own file	2013-12-03 16:00:04 -05:00
version_concern.rb	Attempt to sort based on primary key in scope methods on VersionConcern if primary key is an integer.	2014-04-30 18:13:04 -04:00
version_number.rb	Bump to 3.0.1 [ci skip]	2014-03-14 17:52:17 -04:00