It is for versioning. I have a pair (number, version) as another method to identificate a row in the table, so "number" and "id" are absolutely independent. So, to my mind, more low-level language and libraries are better in this situation.
On Sep 9, 9:17 pm, Marnen Laibow-Koser <rails-mailing-l...@andreas- s.net> wrote: > adrianopol wrote: > > Thanks! Frankly speaking, I've decided to use java for this project. > > It's not good to fight with framework's logic) > > So learn it instead of fighting with it. Anyway, while I'm surprised > that Rails migrations can't do what you want here, I also can't see how > more than one autoincrement field in a table would be useful: if you > have one, then you can calculate all the others from it. > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > [email protected] > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
