On Mon, Jun 30, 2008 at 11:01 AM, Andrus Adamchik <[EMAIL PROTECTED]> wrote: > There is no lazy fetching of attributes (only relationships). We will be > adding it at some point. It is a bit more involved than simply suppressing a > given column in the SQL translator. Still you have a few of options: > > 1. Place large columns in a separate table with 1..1 relationship to the > master table . > 2. Do not map large columns in the ObjEntity and resolve them manually on > demand (either with SQLTemplate, or by mapping a second entity to the same > table). > ...
Thanks! Since I, generally, have no influence over the database table format, then #2 is the way to go. In my case create a "FastFoo" mapping for "Foo" and otherwise leave "Foo" unchanged in the code where performance is not an issue + extract an interface which is common between FastFoo and Foo. It didn't occur to me that it was supported to have multiple mappings to the same database table. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer
