Re: Per-query local timezone

From: Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk>
To: pgsql-general(at)PostgreSQL(dot)org
Subject: Re: Per-query local timezone
Date: 2011-06-14 15:23:15
Message-ID: it7ud5$9no$1@pye-srv-01.telemetry.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> John R Pierce <pierce(at)hogranch(dot)com> writes:
>> On 06/14/11 2:40 AM, Mark Morgan Lloyd wrote:
>>> The development environment I'm working with uses short-lifetime
>>> sessions, and it's proving difficult to get a set command and a query
>>> associated with the same handle.
>
>> this environment doesn't support even a transaction?
>
> Sounds kinda broken :-( ... but maybe Mark could wrap the operations
> he needs into custom functions.

Is always a possibility. The problem is that particular component I'm
using conflates the open and issue-query operations and has an implicit
transaction, the developers are aware that this has undesirable
implications.

--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]

In response to

Browse pgsql-general by date

  From Date Subject
Next Message erwin@darwine.nl 2011-06-14 15:30:28 Re: psql reports back wrong number of affected rows.
Previous Message Edmundo Robles L. 2011-06-14 15:20:30 Executing \i of psql command using libpq library