On 3/13/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
but the main issue in this case is 1-1 relationships are tough for OR mapping layers to optimize. torque frequently performs unnecessary joins across to message_flags. ATM this results in tables scans which may be possible to index away but avoiding the unnecessary joins means hand editing the generated source.
Ah yes of course. Here are two suggestions, don't flame me! 1/ use stored procedures, assuming the db supports them, might restrict the choice of db's to those for which we can write procs. Derby is easy-peasy being Java, I can hack oracle pl/sql, but after that I've shot my bolt. 2/ use views for fast read-only access, assuming that reads are much more common and can be disentangled from writes. d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
