Hello Marnen, I appreciate your insight - it sounds like the voice of experience to me. :-)
I don't actually intend to use this "log_number" attribute as a key in the database. An Assignment will always be unambiguously identified by the id it was "born" with. The log number is important in the analog end of our business, but as far as the database goes it's of similar importance to, say, the floor number in the client's shipping address if that makes sense. We might sort by log_number, we might search for a log_number and we will certainly use it as a reference when we invoice a job and when we rename the files. But I'm not considering it (the log_number) to be a key - just an attribute like the date and time of the shoot. Does that help clarify my goals? Steve > I'd advise you to drop this idea altogether and just use the primary > key. You'll be in for fewer headaches if you have one unambiguous > identifier. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
