On Sat, Feb 21, 2004 at 03:33:45AM -0000, Greg Sabino Mullane wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > >> attribute to allow primary_key_info() to return a single > >> row containing multiple-column information. > > > Out of interest, why did you need a custom primary_key() method? > > To make life easier for application writers who want to take > advantage of it when a primary key is on more than one column. > Instead of returning three rows, we can return one with a > single list of all the columns instead "4,5,1"
I still don't quite follow you. How does it differ to what the default primary_key() method does? > Note that we did not do this with foreign_key_info: it is > complicated enough already! Although the lack of an %attrib > on foreign_key_info is an impediment as well. Can we add one > in to DBI? I was thinking of using a flag to toggle between > ODBC and SQL/CLI. I'll add \%attr to all the metadata methods that don't have one. Tim.
