The server is a Linux machine. In 3.4 beta, inserttable() works
without the None value, but seemingly only if the list is nested
within another list, e.g:
someList = ["test"]
db.inserttable("someTable", [someList])I'm sure these were bugs that were fixed in the official 3.4 and 3.8 releases. I'm probably better off asking for the upgrade so I can use the additional functionality gained in the newer releases. Thanks. Ryan Sobash On Nov 27, 2007 4:45 PM, Christoph Zwerschke <[EMAIL PROTECTED]> wrote: > Ryan Sobash wrote: > > I am using an older version of pygresql (3.4 beta). I am having a > > problem inserting NULL data using inserttable() with this version. I > > am using the Python 'None' type in my list to indicate it should be > > NULL. Is this a known issue with this version of pygresql? Is there a > > way around this (I'm not the sysadmin on the machine and would rather > > not bug them to upgrade)? I coded the program on a machine which had > > pygresql 3.8.1 and it worked fine. > > There was one important inserttable patch in 3.4 which may not be in > your 3.4beta yet and another improvement in 3.8. What operating system > are you using? Maybe we have already a suitable rpm so it will not be a > big problem for the admin. Or maybe you can install a newer pygresql in > your user packages directory and use that. > > -- Chris > _______________________________________________ > PyGreSQL mailing list > [email protected] > http://mailman.vex.net/mailman/listinfo/pygresql > _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
