Christoph Zwerschke wrote:
> The default row type has been changed because a tuple is considered the
> more appropriate, pythonic type for an inhomogeneous collection where
> the order matters. This is also what most other drivers deliver and
> people expect. Named tuples are even more convenient.
>
> Having said this, you can also configure Pygres classic and DbApi2 to
> return lists or any other type instead. I currently have a bad internet
> connection and can't provide the links but please have a look at the
> docs, it should be all explained there.
>
> -- Chris
That's OK. I think this change only affects a very small part of my code
which I've changed to handle the new version.
But my other two emails about the bug in pygresql's parsing of postgresql's
array notation (e.g. '[2:3]={a,b}') and my inability to suppress the automatic
conversion of timestamp with time zone into a datetime.datetime are real
problems for me.
If someone could look into that when they get a chance, it would be
greatly appreciated.
cheers,
raf
_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo.cgi/pygresql
