RE : [log4plsql] Log4plsql extension
Brought to you by:
gmoulard
From: <log...@li...> - 2004-02-23 17:27:14
|
Ashton, You can log xml text in TLOG.LTEXTE with all log4plsq features. and use a XML namspace for now the format. Perapse, there is a problem with a size of the message? About a converting API, you has which prototype thinks? Regards, Guillaume Moulard gmo...@us... Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ and : http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-i= nfo or http://www.mail-archive.com/log...@li... for log...@li... -----Message d'origine----- De : log...@li... [mailto:log4plsql-all= -in...@li...] Envoy=E9 : mardi 17 f=E9vrier 2004 15:29 =C0 : log...@li... Objet : [log4plsql] Log4plsql extension We've been looking at log4plsql for possible use as a standard database l= ogging tool within our organization. We currently have a standard package that we employ, but often find we have to customize it for= our different applications. Log4plsql would appear to address a lot of our needs, with one major exception: our database applicat= ion logging usually employs explicit columns for key value storage; allowing us to join directly in sql from our logging table(s= ) to staging/load tables etc. The query-ability of these data attributes is crucial to us. Having to parse TLOG.LTEXTE for significa= nt values (e.g. keys, parameter values etc.) would be quite onerous. If I were to customize Log4plsql, I'd consider perhaps another table to s= tore some sort of template for the contents of TLOG.LTEXTE (alternatively add an additional column instead) to accommodate= named attributes and a format (xml would be ideal for this). I'd also consider creating an api for converting parameters into the= template format, for use prior to calling plog.error/fatal etc. You may already have considered this, or perhaps someone has already sugg= ested it. Might this be something that someone is already working on? Should we endeavor to create this extension ourselves? Your tho= ughts and comments would be very welcome. Very best regards, Ashton Thorogood Database Team SIG |