×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Walden H. Leverich wrote:
I can't think of a reason I'd design a table today (on any platform)
that didn't include a primary key.
Well, we've had primary keys forever. The problem is that in SQL
"primary" also implies "unique". And even that wouldn't be so bad if it
didn't add a bunch of overhead. By making the database check for
uniqueness even after the program already has, you add unnecessary
overhead. I don't have a problem with defining primary keys, I have
problem with adding overhead.
And if a modeling tool can't figure out how to use a non-unique key,
it's a problem with the tool, not the database.
Again, I'm all for using the right tool, and I'm just as completely
against technological fascism.
Of course, given the fact that DDL defined files underperform so
abysmally vs. DDS keyed physicals, the point is somewhat moot. May as
well stick UNIQUE on the thing, it's all but free.
Joe
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
