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

RE: Transactionless ODBC

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Alex Stewart'" <astewart(at)freedomintelligence(dot)com>
Cc: "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org>
Subject: RE: Transactionless ODBC
Date: 2000-06-07 08:27:31
Message-ID: 8568FC767B4AD311AC33006097BCD3D60917E3@woody.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-interfaces

> -----Original Message-----
> From: Alex Stewart [mailto:astewart(at)freedomintelligence(dot)com]
> Sent: 06 June 2000 17:55
> To: tip(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu
> Cc: pgsql-interfaces(at)postgresql(dot)org
> Subject: Re: [INTERFACES] Transactionless ODBC
> 
<SNIP>
>
> The troubling code is (if I have already posted it, I apologize)
> 
> /*      Begin a transaction if one is not already in progress */
> /*      The reason is because we can't use declare/fetch 
> cursors without
>         starting a transaction first.
> */
> if ( ! self->internal && ! CC_is_in_trans(conn) && 
> (globals.use_declarefetch || STMT_UPDATE(self))) {
> 
> Alex Stewart

I raised this question on the Hackers list last month (after getting no
responses here) and got a message back from Thomas Lockhart saying he
planned to take a look. I believe he's on holiday at the moment but
hopefully he can help when he gets back....

Regards, 
  
Dave. 
  
-- 
Disclaimer: the above is the author's personal opinion and is not the
opinion or policy of his employer or of the little green men that have been
following him all day.
http://www.vale-housing.co.uk/ - http://www.pgadmin.freeserve.co.uk/

pgsql-interfaces by date

Next:From: Mihai GheorghiuDate: 2000-06-07 14:36:37
Subject: Win ODBC drivers for Postgres
Previous:From: Joachim AchtzehnterDate: 2000-06-06 22:31:36
Subject: Re: JDBC squirrely transaction behavior??

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