-----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"
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.
> pg_noprefix?
You are right, they should both be prefixed with "pg_"
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200402201955
-----BEGIN PGP SIGNATURE-----
iD8DBQFANtGzvJuQZxSWSsgRAjJPAKDF/3EiZO2mWyV4gR/tLU7PZnIRvwCg75bD
Bjln62DcvJfupWi5QwBB8eI=
=Peop
-----END PGP SIGNATURE-----
