Patches item #412045, was opened at 2001-03-28 18:31 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=303152&aid=412045&group_id=3152
Category: modules Group: None Status: Open Resolution: None Priority: 5 Submitted By: Vlad Seryakov (seryakov) Assigned to: Kriston Rehberg (kriston) Summary: Sybase Driver Error handling Initial Comment: Here is the patch that allows to catch sybase errors from triggers and stored procedures. ---------------------------------------------------------------------- Comment By: Peter M. Jansson (petej) Date: 2002-03-20 13:02 Message: Logged In: YES user_id=20577 This patch is essential for getting an error message back from nssybpd to the AOLserver for triggers and stored procedures, and getting those errors would not otherwise be possible. However, Sybase often generates multiple error messages for a single operation, and the AOLserver proxy protocol only allows for returning a single message. You'd have to either bundle up all of the Sybase messages into one proxy message (which would make detecting the specific error you got more difficult, since you'd then have to look for the error in what could be a bunch of messages) or you'd have to live with losing some of the errors. (In an older version of nssybpd, the proxy wasn't completing the result loop, so when an error occurred in the next query, you'd often just get an uninformative error that was the last message spewn by Sybase.) By logging all Sybase errors to the syslog or to its own file, no error detail is lost. (Another option would be to change the proxy protocol, but that's beyond the scope of this patch.) As far as the choice between logging to a private file or files versus logging to syslog, it still seems to me that logging to syslog is better. ---------------------------------------------------------------------- Comment By: Vlad Seryakov (seryakov) Date: 2002-03-20 11:54 Message: Logged In: YES user_id=184124 Forgot the patch ---------------------------------------------------------------------- Comment By: Vlad Seryakov (seryakov) Date: 2002-03-20 11:53 Message: Logged In: YES user_id=184124 I added propagation of Sybase erros to AOLserver driver, so Sybase error message would be visible in the log file. ---------------------------------------------------------------------- Comment By: Peter M. Jansson (petej) Date: 2002-03-20 11:42 Message: Logged In: YES user_id=20577 This does not seem to be a good idea, since it would involve re-inventing logging code, especially if multiple instances of nssybpd are to log to the same place (plus, how do you figure out where the log files should go?). Why don't you want to use syslog? ---------------------------------------------------------------------- Comment By: Kriston Rehberg (kriston) Date: 2002-03-20 11:38 Message: Logged In: YES user_id=16427 How possible would it be to get nssybpd to log to its own log file instead of using syslog? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=303152&aid=412045&group_id=3152
