This is a discussion on Re: SQLColAttributes and SQL_DESC_NULLABLE within the pgsql Interfaces odbc forums, part of the PostgreSQL category; --> > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto gsql-odbc-owner@postgresql.org] On Behalf Of Ludek Finstrle > Sent: 06 December 2005 ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto > Sent: 06 December 2005 22:55 > To: Robert Jireš > Cc: pgsql-odbc@postgresql.org > Subject: Re: [ODBC] SQLColAttributes and SQL_DESC_NULLABLE > > > It seems that for SQLColAttributes to return something else than > > SQL_NULLABLE, "Parse Statements" option MUST be turned on. > Am i right? > > For some reason stmt->manual_result is true, which causes that the > > statement is not parsed. What does this stmt->manual_result mean? > > I attach patch which solve this problem. Thanks to Robert to point > it and find the solution. > > I don't know if it works with declare/fetch or server side prepare > (maybe other options could break it too). Please is there someone > who can test it? I can upload Windows DLL to test it if you want. No regressions I can find - patch applied, thanks! *However*, whilst testing I did find an issue with SQLTables that seems surprisingly similar to the one you fixed before. It's pretty easy to recreate in the Microsoft test suite. - Connect to a data source with Declare/Fetch enabled. - SQLExecDirect "SELECT * FROM pg_class" - Get Data All (from the results menu) - SQLTables - Get Data All It never stops retrieving data! Seems that you need to do the SQLExecDirect first - SQLExecute doesn't trigger the problem. SQLColumns is similarly affected - perhaps there are more as well. Wanna take a look, or shall I log a bug until one of us gets time? Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
| ||||
| > *However*, whilst testing I did find an issue with SQLTables that > seems surprisingly similar to the one you fixed before. It's pretty > easy to recreate in the Microsoft test suite. I didn't fix something similar. I don't remember it at least. Could you be more specific? I only point at Prepare, Execute, Execute or ExecDirect, ExecDirect problem. > - Connect to a data source with Declare/Fetch enabled. > - SQLExecDirect "SELECT * FROM pg_class" > - Get Data All (from the results menu) > - SQLTables > - Get Data All > > It never stops retrieving data! Seems that you need to do the > SQLExecDirect first - SQLExecute doesn't trigger the problem. > SQLColumns is similarly affected - perhaps there are more as well. I'm unable reproduce it here. I have CVS source with autocommit_off patch. It stops when I expect. I tried it againist ANSI (debug) driver (PgSQL 8.1 Win) with these options: - SSL Mode = disable - default settings except: - Use Declare/Fetch - checked - MyLog - checked > Wanna take a look, or shall I log a bug until one of us gets time? Please send me your mylog output and driver for testing purposes (maybe zipped source code too ?). Feel free to log a bug. Bug tracer is here for this purpose ;-) Regards, Luf ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |