Skip site navigation (1) Skip section navigation (2)

[ psqlodbc-Bugs-1000630 ] Related to bug GenerateBDDirectMethod fails in VS studio 2005 with ODBC

From: <noreply(at)pgfoundry(dot)org>
To: noreply(at)pgfoundry(dot)org
Subject: [ psqlodbc-Bugs-1000630 ] Related to bug GenerateBDDirectMethod fails in VS studio 2005 with ODBC
Date: 2006-05-28 12:25:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
Bugs item #1000630, was opened at 2006-05-04 08:17
You can respond by visiting:

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Patrick Donelan (patspam)
Assigned to: Ludek Finstrle (luf)
Summary: Related to bug GenerateBDDirectMethod fails in VS studio 2005 with ODBC

Initial Comment:
This bug is related to the bug "GenerateBDDirectMethod fails in VS studio 2005 with ODBC" (

I am posting as a new bug because pgFoundry wouldn't let me attach my logs as a commenter.

I get the same problem with the latest version of the drivers:

I tried making changes to a TableAdapter inside the Visual Studio 2005 DataSet Designer and as a result the TableAdapter lost its automatically generated Update,Insert,Delete queries (GenerateBDDirectMethods).

I have found that if I try to re-create my TableAdapter it always comes back without the GenerateBDDirectMethods. If I try to change the GenerateBDDirectMethods property on my TableAdapter to true, it communicates with my database (PostgreSQL 8.1, running locally under Windows XP), then returns the following error:

The type of the database object does not allow to set GenerateDBDirectMethods to true.

Hopefully during this process the reason is written to the log files (both attached).

Simple Steps To Reproduce
1. Open an existing DataSet in the DataSet Designer (or create a new one)
2. Add a TableAdapter, with a simple query (in my case "SELECT * FROM agent")
3. VS will tell you that it generated everything ok, but when you look at the Properties on the TableAdapter you will see that GenerateDBDirectMethods is false.
4. Try changing GenerateDBDirectMethods to true and VS will throw the error above.

Hope that helps.



P.S. Sorry the mylog is so big. VS makes it grow really quickly. Not sure if that's normal or symptomatic of the bug. Let me know if you can't read 7-zip format. I tried zipping instead but the maximum compressed file was > 2Mb!


>Comment By: Ludek Finstrle (luf)
Date: 2006-05-28 14:25

This seems to be problematic:

[3528]PGAPI_MoreResults: entering...
[3528]PGAPI_MoreResults: returning 100
[3528]STATEMENT ERROR: func=SQLSpecialColumnsW, desc='', errnum=3, errmsg='The cursor is open.'
[3528]CONN ERROR: func=SQLSpecialColumnsW, desc='', errnum=0, errmsg='(NULL)'
[3528][[SQLGetDiagFieldW]] Handle=(3,15a49d60) Rec=1 Id=4 info=(12dda4,12)
[3528]PGAPI_GetDiagField entering rec=1[3528]ER_ReturnError: status = 3, msg = #The cursor is open.#
[3528]	     szSqlState = 'HY010',len=19, szError='(null)'
[3528]PGAPI_GetDiagField exiting 0

I'm not sure why. SQLMoreResults returns 100 only if currres is null and there is no cursor opened when curres is null.

Please could you create new mylog output with attached psqlodbc driver?

I hope Hiroshi will read this. I see another strenge thing. There is 3 times error "The cursor is open.". There is STMT_INVALID_CURSOR_STATE_ERROR reported two times (which is IMHO correct) and STMT_SEQUENCE_ERROR once (which seems wrong to me). I try to change this in attached dll but I think it's no real problem.




Comment By: Patrick Donelan (patspam)
Date: 2006-05-19 04:31

Please let me know if you need any more information about
this bug. I'm happy to help out as much as I can :)




Comment By: Dave Page  (dpage)
Date: 2006-05-14 11:25

Previous bug 1000540 closed as this report is more up to date. Re-assigned to Luf in case he wants it :-)


You can respond by visiting:

pgsql-odbc by date

Next:From: Tom LaneDate: 2006-05-28 15:47:11
Subject: Re: Library General Public Licence
Previous:From: Bart SamwelDate: 2006-05-28 09:59:12
Subject: Re: Library General Public Licence

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group