cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Kienenberger (JIRA)" <>
Subject [jira] [Closed] (CAY-414) Support for (batch) query interception and audit
Date Tue, 24 Sep 2013 20:25:03 GMT


Mike Kienenberger closed CAY-414.

    Resolution: Won't Fix

Ari is correct.  3.x and onward have lifecycle events that should provide the necessary hooks
for performing auditing.
> Support for (batch) query interception and audit
> ------------------------------------------------
>                 Key: CAY-414
>                 URL:
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: Core Library
>    Affects Versions: 1.2 branch
>            Reporter: Andrus Adamchik
>            Assignee: Mike Kienenberger
>             Fix For: Undefined future
>         Attachments: 1.2-audit.patch-2006-09-05-00.txt,
> There is a common need to audit what Cayenne saves to the database. Currently people
implement custom solutions, usually based on inspecting ObjectStore or overriding validateFor*
on DataObjects. Due to a mismatch between object model and DB schema (after all ORM is intended
to hide many DB details, think flattened relationships and such), clean audit is not always
possible to be done that way.
> Ideally the solution should be intercepting BatchQueries, as this is what is being sent
to the database in its raw form. Audit log should be commitable to the DB (two scenarios were
mentioned: log committed in the same or in a separate transaction from the main change).
> The discussion of the possible design started in this thread:
> Not sure if we should implement a standard "cayenne audit" feature, or simply provide
needed extension points and post an audit solution as an example. I am more in favor of a
second option (simple extension point) as the actual audit requirements may vary from app
to app.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message