Hi Christoph,
Yes, all I had to do was add a default value for the typcategory column
for Postgres 8. This is for enabling access to Redshift databases which
run Postgres 8.0.2. So far this patch has worked for me. However I
didn't run the test suite and am looking to install Postgresql 8 on a
host so I can test.
On 07/06/2016 07:31 AM, Christoph Zwerschke wrote:
Am 06.07.2016 um 03:31 schrieb Andres Mejia:
I have a patch which enables communication with Postgresql servers
running v8.0. See attached.
Hi Andres,
thanks for the patch. The modern 5.x versions actually are meant to
support only Postgres 9.x (and are tested only against it). We
maintain a 4.x branch if you still need old Python and Postgres versions.
Is the missing typcategory the only place where Postgres 9 is
currently assumed on the remote server? Did you run the full test
suite against Pg 8 with this patch? In that case maybe we could
support Postgres 8 with that patch on the remote side. We would still
require a modern pqlib on the client side.
Instead of setting typcategory to null, we could also add a simple map
of typtype to typcategory ('a' -> 'A' etc.) so that detecting arrays
and other base types via typcategory would still work.
Also, typcategory was already introduced in 8.4, so the check should
be version < 80400.
-- Chris
_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo.cgi/pygresql
--
Andres
_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo.cgi/pygresql
