Patches item #412045, was opened at 2001-03-28 23: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: Vlad Seryakov (seryakov) Date: 2002-03-20 16: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 16: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 16: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
