cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <>
Subject [jira] Commented: (CAY-1464) Improve QueryLogger to log more information
Date Wed, 14 Jul 2010 11:04:49 GMT


Andrus Adamchik commented on CAY-1464:

Somewhat related is CAY-1173, which will likely be revisited in 3.1 as DI container gives
us more flexibility to implement it. The idea is to provide events at certain points of query
execution, and then support various listeners. Some of those may aggregate all events during
a query cycle and give full diagnostics. The good thing about this design is that by default
it won't incur much performance overhead, but users who need to trace low level details, may
implement their own listeners with more complex logic. E.g. the original motivation for CAY-1173
was to implement JMX monitoring of Cayenne stacks.

> Improve QueryLogger to log more information
> -------------------------------------------
>                 Key: CAY-1464
>                 URL:
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: Core Library
>    Affects Versions: 3.1M1
>            Reporter: Evgeny Ryabitskiy
>            Assignee: Evgeny Ryabitskiy
>             Fix For: 3.1M1
> Since I have to support lot's of applications using Cayenne and usually Cayenne logs
is only information I have about some bugs, I wish to have more information in that logs.
> I think it will be nice to have:
> 1) Information of query that was executed (e.g. name of NamedQuery). To find right query
in thousands...
> 2) Result of Select query.
> 3) As much information as it could be collected while logging errors.Like:  What query?
Params? What Query String was build? Connection pool State? Driver version? Cayenne version?
Better more than less.... 
> Last one can be very useful since on production I have only ERROR logging level. And
sometimes it is not possible to enable INFO level to find out what happen. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message