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

(Fwd) Re: ODBC SQLSetPos Delete problem

From: "Lothar Behrens" <lothar(dot)behrens(at)lollisoft(dot)de>
To: pgsql-odbc(at)postgresql(dot)org
Subject: (Fwd) Re: ODBC SQLSetPos Delete problem
Date: 2004-09-14 19:13:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
------- Forwarded Message Follows -------
From:           	Self <Single-user mode>
To:             	pgsql-odbc-owner(at)postgresql(dot)org
Subject:        	Re: [ODBC] ODBC SQLSetPos Delete problem
Date sent:      	Tue, 14 Sep 2004 21:12:53 +0200

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org on behalf of Lothar Behrens
> Sent: Tue 9/14/2004 6:07 PM
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] ODBC SQLSetPos Delete problem
> > I can try to debug the ODBC library, but I do not understand the full
> > source, so I need a little help.
> Unfortunately that is the problem - there isn't anyone left on the
> project who really understands the source code, and in fact the cursor
> code is very experimental and was one of the last features worked on by
> the last guy that did know what he was doing :-(

For that state, it works 'good' in my eyes :-)

> I have (very) limited time right now, but if you let me have some more
> details of the problem I'll see if I can help at all (no promises
> though).

At my current understanding and with comparsion to other databases
and their ODBC drivers (MSSQL), I would force a

SQLSetPos(). [Microsoft][ODBC SQL Server Driver]Cursor operation
conflict, SQLSTATE=01001

The ODBC documentation says, that no or more than one row were
deleted or updated. But it really has deleted one row in my sample

This driver didn't crash.

As for my initial posting in this thread, I know where the crash
happens and for my last posting, I know that a pointer has 0xdddddddd.

Why not handle this pointer as a NULL pointer, because it might be
deleted prior ?

I would try this and also try to figure out when the pointer gets to
0xdddddddd and if I find a solution, it would help to fix this.



> Regards, Dave
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?

---- My home: -----------------------------
Lothar Behrens    | Independent:       lothar(dot)behrens(at)gmx(dot)de
Rosmarinstr 3     | My public project:
40235 Düsseldorf  |
                  |  -> Need comments, please visit :-)

pgsql-odbc by date

Next:From: Greg CampbellDate: 2004-09-14 19:34:14
Subject: Re: ODBC SQLSetPos Delete problem
Previous:From: Lothar BehrensDate: 2004-09-14 18:49:22
Subject: Re: ODBC SQLSetPos Delete problem

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