Hi all!
I just realized the following behaviour in postgresql: when I violate any
constraint (unique constraint in my case) then the transaction is not usable
anymore. Any other sql command returns a "in failed sql transaction" error.
All other databases I used up to now just ignore the statement violating the
constraint, but leave the transaction intact.
Is this intended behaviour or rather a bug? Or is there any way to "switch on"
the behaviour I'd like to see?
Best regards,
Ralf.
--
Ralf Wiebicke
Softwareengineer
exedio GmbH
Am Fiebig 14
01561 Thiendorf
Deutschland
Telefon +49 (35248) 80-118
Fax +49 (35248) 80-199
[EMAIL PROTECTED]
www.exedio.com
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
