| From: | <bmccoy(at)chapelperilous(dot)net> |
|---|---|
| To: | andrew(at)ugh(dot)net(dot)au |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Making changes visible to other connections |
| Date: | 2000-10-10 11:12:42 |
| Message-ID: | Pine.LNX.4.10.10010100711170.13021-100000@chapelperilous.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 10 Oct 2000 andrew(at)ugh(dot)net(dot)au wrote:
> If I run an UPDATE operation from one connection the changed data is only
> visible from that connection. How do make the change visible from other
> connections? Do I have to wrap everything in a transaction?
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.
Brett W. McCoy
http://www.chapelperilous.net
---------------------------------------------------------------------------
The problem with the gene pool is that there is no lifeguard.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | andrew | 2000-10-10 11:34:31 | Re: Making changes visible to other connections |
| Previous Message | Peter Mount | 2000-10-10 10:26:46 | Re: Re: JDBC Performance |