That is an interesting requirement although when I look back I think almost every system I ever worked with had a column named ID in each table. Here at work the inhouse framework they make use us, pretty much requires the PK of a table be just ID and numeric. There are ways around it but they are never used and probably not even known by most.
On 6/22/05, Ken Ferguson <[EMAIL PROTECTED]> wrote: > > Yeah, I'm working with a guy who has, as part of his coding guidelines, > the requirement that every table in the database have a column named ID > that is set as an auto-increment. That's only one of the many fun little > guidelines to which we're strictly adhering. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:210238 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
