From: | Andy Colson <andy(at)squeakycode(dot)net> |
---|---|
To: | Henri De Feraudy <feraudyh(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Basic question on PGSQL and Transactions |
Date: | 2010-09-29 16:38:34 |
Message-ID: | 4CA36B8A.3050602@squeakycode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/29/2010 11:31 AM, Henri De Feraudy wrote:
> Hello,
> I've been writing an application that allows me to edit simple maps. It
> involves Postgis but here I think I have run into
> a basic Postgres consideration.
> I did a bit of editing of a map which involved creating a polygon with a
> selection, inserting into a database and reloading
> the "layer" where this geometric information lies.
> There I was editing quite happily for about an hour and a half. I left
> my application and came back to it in the evening:
> all my work was lost.
> Could this be due to the fact I had not committed my insertions to the
> database?
> I mean, if you are inserting into a table from PLPGSQL do you have to do
> an explicit commit at some stage?
> I'm really quite a newbie as you can see.
>
Yes, you really must commit.
Now, sometimes, some languages/tools will "help" you and autocommit. It
depends on what language/tools/etc you are using.
This is a wookie! If that does not make sense, you must commit!
-south park, slightly paraphrased
-Andy
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-09-29 16:46:20 | Re: Basic question on PGSQL and Transactions |
Previous Message | Henri De Feraudy | 2010-09-29 16:31:57 | Basic question on PGSQL and Transactions |