Niclas Hedhman wrote:
On Mon, Apr 6, 2009 at 3:29 PM, Rickard Öberg <[email protected]> wrote:
the EntityTypeRegistry to find out the type of the property. The value would
then go Long->String->Long, which is not superefficient.
This is certainly doable though, and the benefits of it might be more
important.
Could we handle primitive types differently??
For instance;
public interface PersistentState
{
Object rawObject();
String toPersistable();
}
But where would this be used? If it is for setProperty(name,
persistentState) it is fine, but then "PersistentState
getProperty(name)" is not fine, since then the EntityStore needs to know
how to deserialize the String to the raw object!
It might also be a significant performance hit to use these wrappers on
the property level. We're already creating tons of small objects to
handle entity state!
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
