If we are to bring this to Cayenne as a feature, I am very much in
favor of an generic solution with the ability to define arbitrary
metadata in the model. It has been mentioned in this thread already
that this is a very popular request, and as usual my reply is
"someday" :-/
Andrus
On Aug 20, 2008, at 4:34 PM, Øyvind Harboe wrote:
> On Wed, Aug 20, 2008 at 2:44 PM, Andrus Adamchik <andru..bjectstyle.org
> > wrote:
>> So this is not about syncing with DB defaults?
>
> Nope.
>
>> Then I think that's over-engineered. Would it be easier to simply
>> override
>> needed getters per entity class and do "return super is null ?
>> defaultVal :
>> super", without changing Cayenne core?
>
> That of course gives the user no user interface to
> browse through the model to figure out how defaults are handled +
> scatters boilerplate code all over the subclasses.
>
> Perhaps there is some other way to achieve this?
>
> The crucial bit is to be able to tabulate handling of default
> values. Perhaps
> use a custom base class for all the CayenneDataObject subclasses and
> override readProperty() to handle null pointers via a lookup...
>
> --
> Øyvind Harboe
> http://www.zylin.com/zy1000.html
> ARM7 ARM9 XScale Cortex
> JTAG debugger and flash programmer
>
This archive was generated by hypermail 2.0.0 : Wed Aug 20 2008 - 13:55:03 EDT