Re: bad practice to have a primary key field whose value changes?

2001-10-31 Thread Bennett Haselton
At 02:32 PM 10/30/2001 -0700, Steve Meyers wrote: What would be ideal would be to use auto-incremented numeric fields as primary key fields, and then have a special field in each table designated as the user-friendly field. That way, when you want to view the contents of a table, the

RE: bad practice to have a primary key field whose value changes?

2001-10-30 Thread Johnson, Gregert
Use a join query, rather than separate single-table queries: SELECT a.*, n.url FROM articles a, news_sites n WHERE a.news_site_key = n.news_site_key; -- Greg Johnson -Original Message- From: Bennett Haselton [mailto:[EMAIL PROTECTED]]

Re: bad practice to have a primary key field whose value changes?

2001-10-30 Thread Steve Meyers
On Tue, 2001-10-30 at 13:10, Bennett Haselton wrote: I'm creating a database where one of the tables stores data about news Web sites, and I'm using the URL of the site as a primary key field. This field value might change occasionally. I'm wondering if this is bad practice, especially