chewmanfoo wrote: > If it's immutable, then why is it in a database? What he's saying is that it is "immutable" by policy. If you have a database that stores orders where each order contains an order number (not a primary key, but rather a number given to a customer), by policy that order number should never change. If it did you would lose track of the order.
This has nothing to do with position in the database. Order number is simply a reference to one specific order. A reference that *must* be immutable and atomic. -- Posted via http://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.
