if one uses the ID's then can I assume you should then "force" the ID's to be set as you want them in the migration? i.e. can't rely on a standard rails migration where the database uses it auto-increment?
On Mon, Dec 22, 2008 at 7:25 AM, Maurício Linhares < [email protected]> wrote: > > On Sun, Dec 21, 2008 at 5:39 PM, Greg Hauptmann > <[email protected]> wrote: > > Hi, > > What's a good approach for referencing lookup/reference data (static) > that > > one has loaded in a reference table. Say for example "tax codes", which > > pretty much have just the database ID and then a description field. Some > > options that come to mind: > > 1 - By ID - however this makes an assumption that the data always loads > into > > a database and gets the same IDs (i.e. when you're loading your static > > reference data)? > > If the descriptions change, you should do it just like this. > > > 2 - Search by description to identify the record - but obviously if one > > changes the description this isn't very good. > > That's the simpler way to solve the issue, if the descriptions do not > change. But this isn't really "beautiful" from the database point of > view, as your data isn't going to be normalized and I usually prefer > to work with normalized data unless denormalization is needed. > > > 3 - Perhaps create a specific identify/key as a new column that you use, > but > > is not the database Rails ID? How's this sound? > > > > I think this is a way to complex way to solve a simple problem :) > > - > Maurício Linhares > http://alinhavado.wordpress.com/ (pt-br) | http://blog.codevader.com/ (en) > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
