On 1/3/06, Perrin Harkins <[EMAIL PROTECTED]> wrote: > In my opinion, this kind of artificial key is an unnecessary kludge. > The multi-column key is already a unique identifier, and the database > enforces it. > > - Perrin >
In general, I believe you. . But, for Class::DBI, ??? My experience has been it is less Kludgy in Class:;DBI to just make a single column PK for tables that would have Multiple Keys than to not use the relationship. This is mainly true when you need the meta_info perhaps as accessors to related rows from tables of any sort are easy as just call retrieve as you have pointed out. -- pjs ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Maypole-users mailing list Maypole-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/maypole-users
