severity 357931 wishlist thanks hi
in sql-editor 0.17 I disabled the (nonworking) support for PostgreSQL ; this is a workaround, since I do not use MySQL any more, and I never used PostgreSQL; so I would need help in solving this issue. For this reason I am downgrading the bug severity. On Mon, Mar 20, 2006 at 08:30:39PM +0100, Micha Lenk wrote: > Python now > has a [0]database-API which would probably better fit the approach of > abstracting the concrete database implementation stuff. > 0. http://www.python.org/doc/topics/database/ > http://www.python.org/doc/peps/pep-0249/ The spec at [0] , a.k.a "DB-API spec v2.0" , has been around since Apr 1999: you are using "now" in a quite wide way :-) sql-editor uses python-mysqldb ( http://sourceforge.net/projects/mysql-python )for MySQL and python-pgsql for PostgreSQL and both are advertised as being faithful to "DB-API spec v2.0" "DB-API spec v2.0" does not include, though, all needed commands ; one example is a command to list the available tables; and indeed sql-editor fails on PostgreSQL for that reason > Using this API > could maybe enable support for a big [1]bunch of databases at once. :-) as this bug shows, this is definitevely not true > Sorry, but I currently haven't enough time to do it. me too > I just wanted to report the issue. :-/ thanks anyway a. -- Andrea Mennucc
