We've been doing a bit of work on Torque and have some things that might
be of interest as patches. Any interest in the following:
1) Modifying Torque.init(String fileName) so that it searches on the
classpath for the fileName.
The patch (I think) would be to add a new method:
Torque.init(String fileName, boolean searchOnClasspath)
{
// either load normally
...
// or load from classpath
}
and then have Torque.init(String fileName) call the new function.
2) One of the frequent issues we have is to create a "logtable" for all
transactions to a table - essentially, create almost a duplicate of the
table and use triggers to populate it on INSERT, UPDATE or DELETE.
I've modified the database.dtd to include a "createLogTable"
parameter for the table object, and if it's set to "true", I generate
the logtable and all associated triggers/functions. (Currently only
working in Postgres and Oracle.)
Personally, I'm not sure #2 should really be part of the central
product, but it is really useful for us.
Just offering my two cents to help a fabulous product along.
-Peter Hamlen
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
