On 14/04/2009, at 6:30 PM, Andrey Razumovsky wrote:
I'm afraid I don't actually catch the point. This sounds like two
separate
tasks.
Comments that are (re) engineered to SQL comments cannot be generic,
because
as far as I know, SQL specifies only one string per column, table etc.
Generic properties are more flexible, but they cannot be saved in
DB. And I
don't like the idea of having generic property map this one "specific"
comment key, because it makes the design blurry. So possibly we
could open
both tasks (?)
Do you mean comments which will actually be passed to the database
engine? Is this for auditing or logging? If so, I'd suggest that maybe
they are a completely different feature to CAY-400 since the core of
Cayenne will have to understand how to apply them.
Although we could reserve certain keys (eg. cay-javadoc, cay-
SQLcomment) generic key-values is going against the XML paradigm and
it might be better to just have special GUI elements for special
things like these.
Ari Maniatis
-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001 fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
