>>> Query 3 >>> I know the hazards of using floats. .....they will ditch me on >>> customer's machine only.....but I have already written some 20 >>> migrations using float as data type.. Is there any safe way to >>> rescue >>> if I know I am storing the price and it will always be within 0 and >>> 9999(.00) >> >> Safe way to rescue? Not sure I follow. Why not write another >> migration that converts all of those float fields into decimal >> fields? >> >> -philip > > I agree with you Phillip. I am switching to decimal. My project is in > early stage. Instead of adding one more migration I want to change the > migrations itself. > I certainly would do it after > > $rake db:rollback > > I hope that should not create any issue. > the reason i want to avoid adding another migration is it will create > another confusion for future developers
If you're in the early stages of development and redoing a migration won't mess up anything, there's no harm in doing it. I do that all the time. Many times I'll create a handful of migrations early on, adding fields here and there and then once it's all gelled and I'm happy will merge them all into an initial migration -- for the exact reasons you mentioned. The only time this isn't an option is if you've deployed to production and would lose changes or if it would seriously mess up other developers. -philip --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
