While I am sympathetic to your cause I am not very happy about the OTHER
type.
Why?
Well, what happens when an other language accesses a column like that.
That issue is already concrete when using the ODBC connectivity from
let's say php.
Also there is an other type in jdbc spec called JAVA_OBJECT.
What the heck is that all about?!?
I just feel that a true DBMS should be language neutral and define
a clear datamodel that everybody can understand and interpret.
What is the literal representation of OTHER type's value?
When reading, it could be the output of toString() method but
would that work when inserting a value?
That would require a contract that the class has a constructor that
takes a single string value that constructs the same object.
new Other(other.toString()).equals(other) == true
Further should the OTHER type be also comparable (implement comparable
interface)?
Are you sure you can't decompose the data that your object houses into
proper types in database?
Or are you just wishing to dump a whole lot of information into database
quickly
without too much hassle?
- Rami
Joonas Pulakka wrote:
When using the OTHER data type (serialized Java objects), do
expressions (i.e. NAME='Hi') compare simply the serialized byte array
(for exact equivalence), or is the (deserialized) object's equals
method used? If equals is not currently used, could it be added as
feature request?
Thanks,
Joonas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
