Zeugswetter Andreas writes:
> I meant: why is a transaction always open in an ecpg program
Because this is how it works with other embedded SQL systems too. I have
done quite some work with Oracle, and it always has the transaction open.
Keep in mind that there is no disconnect command. Instead you go out by
issuing a commit.
> Yes, but this is handeled implicitly by the backend even if the user does not say
> begin work;
> commit work;
> In that sense every statement is atomic.
> In a client server environment the implicit begin work; commit work; can save
> a lot of time since it saves 2 network roundtrips.
> And of course it would be bad practice if the user is forced to do commit work;
> and then for ease of programming and execution speed only does this every 100 statements.
> What I am saying here is, that an ecpg program should be able to run with
> autocommit mode on. (Michael Meskes)
I tend to agree. But all embedded SQL programs I've seen so far only use
commit. I never saw one that issues a begin work since I stopped using
Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH
meskes(at)topsystem(dot)de | Europark A2, Adenauerstr. 20
meskes(at)debian(dot)org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 1998-03-25 14:52:19|
|Subject: Re: AW: [HACKERS] Re: PostgreSQL reference manual|
|Previous:||From: Bruce Momjian||Date: 1998-03-25 14:46:38|
|Subject: Re: [HACKERS] Feature: output index name in explain ...|