URL:
<http://savannah.gnu.org/bugs/?27823>
Summary: SQLClient drops connections without sending
notifications
Project: GNUstep
Submitted by: kaicats
Submitted on: Di 27 Okt 2009 12:04:04 GMT
Category: Libraries
Severity: 3 - Normal
Item Group: Bug
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
Scenario:
You have a connection to a PostgreSQL server.
The server issues an error.
Postgres.m will then close the connection and raise an exception, but will
not send out a SQLClientDidDisconnectNotification. For that matter, I've never
seen a SQLClientDidConnectNotification either. Presumably that never happens
with automatic connects.
This is rather important when there's a need to start every connection with
stuff like SET client_encoding = 'UTF8'.
Anyway, it seems rather unfriendly (and performance-hostile) to drop the
connection just because there was an error. You cannot always avoid, say,
causing a duplicate key error, in a situation where more than one connection
is updating.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?27823>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
