Well, I started looking at it and determined that the only way for us to
truly log the queries would be to essentially make our own wrappers over
Statement and PreparedStatement. There are projects (log4jdbc, notably) that
already do this, and in a transparent manner. I'm not sure that adding a
whole bunch of SQL logging directly to Lift is better than leveraging some
existing libraries to do it.
Derek
On Thu, Aug 6, 2009 at 11:03 AM, marius d. <marius.dan...@gmail.com> wrote:
>
> Yeah we're aware of that. That is based on toString application which
> is JDBC driver dependent. I think Derek started some work on this to
> correct this behavior. Derek ?
>
>
> Br's,
> Marius
>
> On Aug 6, 8:01 pm, jon <jonhoff...@gmail.com> wrote:
> > Hi,
> >
> > I have the following in boot:
> > DB.addLogFunc((query, len) => Log.info("The query: "+query+" took
> > "+len+" milliseconds"))
> >
> > I was expecting the query parameter to be sql, but it's actually some
> > sort of guid
> >
> > "INFO - The query: 6839c016-0122-f09a-9c96-0000003844e8 took 5
> > milliseconds"
> >
> > Any ideas?
> > I'm running with derby.
> >
> > Thanks,
> >
> > Jon
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---
