Re: Making changes visible to other connections

From: andrew(at)ugh(dot)net(dot)au
To: bmccoy(at)chapelperilous(dot)net
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Making changes visible to other connections
Date: 2000-10-10 11:34:31
Message-ID: Pine.BSF.4.21.0010102132150.41582-100000@starbug.ugh.net.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 10 Oct 2000 bmccoy(at)chapelperilous(dot)net wrote:

> I would venture to say yes. If you are doing any kind of multi-user
> activity, you should be using transactions and committing or rolling back
> your data to maintain integrity. This applies whether you are using
> libpq, DBI, ODBC, or whatever.

Ahh OK. I was hoping I wouldnt have to for single statement transactions
as there is nothing to roll back if it fails. I'll try it and see how I
go.

Thanks,

Andrew

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrew.Mason 2000-10-10 11:37:14 Installation problem
Previous Message bmccoy 2000-10-10 11:12:42 Re: Making changes visible to other connections