On Sat, Oct 21, 2006 at 09:59:36AM +0200, Fabian Groffen wrote:
Hi all,
I probably missed something, but after the recent commits some questions popped up: - why sql_logdir -> logdir? Well the idea was to merge both xquery and sql logs. - why was this solution not a good idea wich led to a revert and addition of xquery_logdir? Problem is the logs of both frontends are managed differently, ie xquery simply wants the logs in the BBP dir and let the BPP commit cleanup the log files. This looks like a real design error. Log files are preferable in a failsafe environment, definitely not on the same disk as the database itself. Moreover, GDK should not be polluted this way with XQuery specifics. It should be handled from a PF-module. Obeying our policy to keep
Niels Nes wrote: transaction level stuff as high as possible in the software stack.
SQL has a manager thread which saves bats to disk and then cleans up the logs. This is a much cleaner approach!
As both frontends do not know about each other nor about how they manage the active bats, its better to keep the logs seperate (and log managing (logger)).
Current idea is to have a single interface (logger module), which will be used by both xquery and sql. But the actual files and bats created by the seperate instances of the logger object, will be seperate.
Niels
Not that I don't agree, but I think it's good to know at least why/what is the problem.
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers