On Wed, 24 May 2006 12:05:45 +0200 Christoph Zwerschke <[EMAIL PROTECTED]> wrote: > Paul Hide wrote: > > I am experimenting with pygresql as an alternative to pyPgSQL. So far, > > it has been a good experience. However, I was surprised to see that > > pg.pkey only returns one attribute/column name of a table that has a > > composite primary key. > > I think PyGreSQL never supported composite primary keys in pkey() and > get(). A backward compatible fix would be to let pkey() return the name > of the primary key if it is a single column, or a tuple of column names > if it is a composite key. get() should cope with composite keys as well, > and also allow tuples for the keyname attribute. > > If nobody disagrees, I'll try to add this over the weekend. This could > then go into PyGreSQL 3.9.
Seems like a good idea but can you wait? There are a few buglet fixes that should really be released before adding a new feature. I will try to package things up this weekend. -- D'Arcy J.M. Cain PyGreSQL Development Group http://www.PyGreSQL.org _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
