Make timestamped migrations optional
Reported by Andrew Stone | June 18th, 2008 @ 05:37 PM
Have the next_migration_string check for a config option to determine migration number formatting:
config.active_record.timestamped_migrations = true
I think the default should be false due to the "legacy" applications.
Comments and changes to this ticket
-
Andrew Stone June 18th, 2008 @ 05:38 PM
- no changes were found...
-
Andrew Stone June 18th, 2008 @ 05:40 PM
I didn't see the attachment, just noticed where references it on the screen. I removed the duplicate attachment.
-
Andrew Stone June 18th, 2008 @ 05:50 PM
Forgot to add:
cattr_accessor :timestamped_migrations , :instance_writer => false
@@timestamped_migrations = false
This is required (as you guys know), in activerecord/lib/active_record/base.rb
Apologies, it's my first attempt at submitting a patch.
-
-
Pratik July 9th, 2008 @ 01:24 PM
- → Tag changed from “” to “patch”
- → State changed from “new” to “incomplete”
- → Assigned user changed from “” to “Pratik”
The default needs to be true.
Also, it'll be nice if you could send an email to rails core list to discuss this change.
Thanks.
-
Andrew Stone July 11th, 2008 @ 02:32 PM
I just sent an email to the core list. Is this why it was marked as incomplete?
thanks,
andy
-
nikz July 17th, 2008 @ 02:42 AM
- no changes were found...
-
nikz July 17th, 2008 @ 02:42 AM
Uploaded a diff that flips the default and adds docs, so us luddites can have our numbers back ;)
Now you kids get off my dang lawn!
-
Repository July 17th, 2008 @ 02:57 AM
- → State changed from “incomplete” to “resolved”
(from [bbab6391366f59189e84d2b8de2a63bea91a9851]) Set config.active_record.timestamped_migrations = false to have migrations with numeric prefix instead of UTC timestamp. [#446 state:resolved]
Signed-off-by: Pratik Naik
-
-
Repository July 30th, 2008 @ 05:44 PM
(from [af3f2aad7ecb31a6e1d09f06775cb33b4ad64d91]) Set config.active_record.timestamped_migrations = false to have migrations with numeric prefix instead of UTC timestamp. [#446 state:resolved]
Signed-off-by: Pratik Naik
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too"..
