db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Dudziak (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OJB-24) Feature Request: enumerates and field conversions
Date Mon, 18 Apr 2005 21:08:46 GMT
     [ http://issues.apache.org/jira/browse/OJB-24?page=comments#action_63113 ]
Thomas Dudziak commented on OJB-24:

Ok, I guess you'd like an extended FieldConversion interface that not only has the object
(sql or java) but also the field descriptor (from there you can reach the class descriptor
and so forth) ? Mhmm, this might be easily achievable via something like dependency injection,
e.g. a setFieldDescriptor method at the field conversion class iff it implements a FieldConversionExt
I'll have a look at it.

> Feature Request: enumerates and field conversions
> -------------------------------------------------
>          Key: OJB-24
>          URL: http://issues.apache.org/jira/browse/OJB-24
>      Project: OJB
>         Type: New Feature
>   Components: PB-API
>     Versions: 1.1 CVS
>     Reporter: Martin Taal
>     Priority: Minor
>  Attachments: EMFEnumerationConverter.java
> Hi,
> In my model I have enumerates which are represented as a java object in memory. An enumerate
java object has an int and a String value. When the owner object is persisted I want to convert
the enumerate object to either the int or the string and store it in a field. When the owner
object is retrieved then the primitive type database field should be translated into the enumerate
> It seems logical to use fieldconversions to achieve this, however the field conversion
interface only passes the value from the database and from this database value it can not
be determined which Enumerate object should be created. This is so because different enumeratetypes
can have the same value (with a different meaning). To identify which enumerate object should
be created the fieldconversion interface could be extended so that also the field descriptor
is passed.
> This is really just a very-low-priority-nice-to-have because there are many workarounds,
e.g. store the enumerate class in the field also (etc.). But maybe somebody else also requires
it or this has come-up earlier or maybe field conversions are looked at anyhow for a new larger
> gr. Martin Taal

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

View raw message