Thomas Fischer wrote:
Thanks a lot for your explanation, now I see what you have in mind.
My current feeling is that this is outside the scope of Torque. I do not
see any additional benefit to include the ColumnValueConverter into
Torque as compared to using it standalone. It is not the job of a Object
relational mapper to provide String representations of objects; there
are other libraries which do this, e.g. jakarta common's betwixt.
You are right but nevertheless I find the inclusion of the
abovementioned methods useful. Two reasons:
- It would make the API more regular.
- I can imagine several use cases (including one of mine) where setting
column values from a BaseObject could be nice.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
