Thanks, that looks promising. I just began to think about that option.
Any other possibilities?
I was thinking about the making use of the recovery subsystem which might be of help on interpreting the Log. Could this be viable?
On 5/4/06, Bryan Pendleton <[EMAIL PROTECTED]> wrote:
> I am tring to build an application that captures changes in Derby
> database.For example, as a new query inserts data to some table comes, I
> want to be able to get that change without using trigger for scalability
> and loose coupling reasons.
What about using something like P6Spy (http://www.p6spy.com) to wrapper
your JDBC driver and inspect all the calls that way?
thanks,
bryan
