Joe,

Good catch. I rechecked. Don't know what happened (forget to recompile
after changing source???). But I deleted the table and recreated it using
the DDS as unique key. Now it is closer to the SQL constraint. Good news
/ bad news. Good news - SQL is not the culprit. Bad news - some people
may use this information to continue not having keys on a physical file
(even though 95+% of their updates will involve some use of a key anyway).

12.289
12.280
12.136

However, if I add this "standard" logical
R IIMJOER PFILE(IIMJOE)
IPROD 25A
K IPROD
Against that same physical file then you will see the same times.
12.199
13.313
12.277

So, why not just have the UNIQUE key on the physical?


Rob Berendt

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].