Justin Clift said:
> Christopher Browne wrote:
>> I've had to add some "new stuff" to the "altperl" scripts to cope with
>> the fact that "SET ADD TABLE" isn't 'smart' enough to detect candidate
>> primary keys.
> <snip>
>
> Would the best approach be to look at improving SET ADD TABLE to detect
> candidate primary keys then?

I'm not sure that there is a strict "best approach."

For some immediate needs, I built some queries to find MY set of ideal
indices.  (Having some systems to migrate from eRServer, the existing
tables all already have a candidate PK on an integer field, _rserv_ts.)

A table may easily have multiple candidates primary keys, and that leaves
room for debate as to which one is preferable to choose.  From a
performance perspective, something on a single integer field would be
ideal.  Something else could be "logically" preferable.

I'll see if I can put together a query to extract some useful table/index
combinations; that should help the "gentle user" to pick from their set of
candidates in the short term.  That may also be the long term solution.
-- 
(reverse (concatenate 'string "ofni.sailifa@" "enworbbc"))
<http://dev6.int.libertyrms.info/>
Christopher Browne
(416) 646 3304 x4124 (land)