Thread: Re: [ psqlodbc-Bugs-1000476 ] DateStyle and Transaction

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Ludek Finstrle
> Sent: 10 December 2005 06:05
> To: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] [ psqlodbc-Bugs-1000476 ] DateStyle and
> Transaction
>
> > You can respond by visiting:
> >
> http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000476
> &group_id=1000125
> > Category: None
> > Group: None
> > >Status: Closed
>
> Are you sure Dave about close this bug? I don't think so.
> See this thread about the topic:
> http://archives.postgresql.org/pgsql-odbc/2005-12/msg00114.php

Ack sorry - that's what you get for trying to work late at night! I've
re-opened the tracker until we decide if the behaviour with the patch is
100% correct or not. At very least it's 50% better than before :-)

> Do you think it's good idea to do explicit begin, commit around
> connect settings all the time? I don't have time for test
> this behaviour yet.

Probably wouldn't be a bad idea - at the very least one tx with all the
hard-coded queries, then one for any user-supplied connect string. I'll
try to find some time to look in the next few days (pretty busy
releasing pgAdmin 1.4.1 and PostgreSQL 8.1.1/8.0.5 for Windows atm).

Regards, Dave

> > Do you think it's good idea to do explicit begin, commit around
> > connect settings all the time? I don't have time for test
> > this behaviour yet.
>
> Probably wouldn't be a bad idea - at the very least one tx with all the
> hard-coded queries, then one for any user-supplied connect string. I'll
> try to find some time to look in the next few days (pretty busy
> releasing pgAdmin 1.4.1 and PostgreSQL 8.1.1/8.0.5 for Windows atm).

You haven't to code it. I ask only for opinion from other developers.
I take a look on in after I study SQL[GS]etStmtAttr. I don't write
code today. I study ODBC specification because I want to clean up
the code.

Luf