Thanks for these interesting articles. I was blind ! Why using a small integer surrogate primary key instead of two chars primary key, why ? =) As described in the article, I think I am abusing of surrogate primary keys. Our database schema is not yet finalized, I am going to fix this right now.
Nevertheless, in some others tables of our schema, I think a surrogate can not be avoided. It will appear in some others tables and I am expecting millions of entries. That's why I prefer a small integer surrogate primary key instead of a 50 or 100 bytes string primary key. In such cases, I was asking about an elegant way to find the unique name along the surrogate primary key. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
