From: | "Flavio Palumbo" <f(dot)palumbo(at)silmasoftware(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | strange commit behavior |
Date: | 2008-11-18 09:01:37 |
Message-ID: | F316DDACBDDA4AEDAC3A8A85887BDF2B@PALUMBOXP |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi all,
I developed a little tool in Java that updates databases throught text
files.
In this tool there is an option that allows the user accepts a defined
amount of errors and save the well formed data.
To do this I start commitment control when the process begins and, at the
end, if the thershold is not reached or there are no errors I commit data,
else rollback.
I tested this tool under MySql and Oracle and everything went as expected.
Unfortunately postgres seems to work in a different way, cause if there is
just one error while the transaction is active I'm not able to commit the
well formed data in the db, no matter if the good records were inserted
sooner or later the error.
Does this behavior appears right for postgres ?
There is any way or workaround to achieve my goal ?
Any hint would be appreciated.
Flavio
-----------------------------------------------------------
Il presente messaggio non costituisce un impegno contrattuale tra SILMA S.r.l. ed il destinatario.
Le opinioni ivi espresse sono quelle dell'autore.
SILMA S.r.l. non assume alcuna responsabilita riguardo al contenuto del presente messaggio.
Il messaggio è destinato esclusivamente al destinatario.
Il contenuto e gli allegati sono da considerarsi di natura confidenziale
Nel caso abbiate ricevuto il presente messaggio per errore siete pregati di comunicarlo
alla casella segreteria(at)silmasoftware(dot)com(dot)
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2008-11-18 09:10:01 | MS Access and PostgreSQL - a warning to people thinking about it |
Previous Message | Flavio Palumbo | 2008-11-18 08:50:46 | strange commit behavior |