|
|
Ruby on Rails: Core |
+ # Specify whether or not to use timestamps for migration numbers > I hope timestamped migrations are made optional in the next release of > -- Koz > Pratik suggested I send an email to this list to discuss making timestamped It's marked incomplete because you've got the defaults backwards. UTC
> migrations optional. I have submitted a ticket which includes a patch. I
> am a bit confused why the ticket was marked as incomplete as the solution
> seems rather simple. IMHO, making this optional would have saved the effort
> of removing code.
migrations should be the default:
+ cattr_accessor :timestamped_migrations , :instance_writer => false
+ @@timestamped_migrations = false
> There are other minor issues, but don't think there's a need to get that I like the idea of the configuration option, just flip the default and
> picky, this should be example enough.
get some feedback from other potential users to make sure it makes
sense to them.
> In the future, should I submit a ticket first or just post something to this Generally a ticket is fine if it's a bug fix or something 'obvious'.
> list?
But if you want to add an option or get some ideas about a new API or
have a change in mind that might be controvercial, then this list
should be your first port of call.
> Thanks for all the work, Rails saved me from the Java world. :) --
> Rails, but if not, I have a way around it. I'm writing this for other Rails
> users more than myself.
> -andy
> Andrew Stone
Cheers