Pluggable "null" definition for persistent fields
-------------------------------------------------
Key: OJB-105
URL: http://issues.apache.org/jira/browse/OJB-105
Project: OJB
Type: New Feature
Components: PB-API
Versions: 1.0.4
Reporter: Martin Kalén
Assigned to: Martin Kalén
Priority: Minor
OJB 1.0.4 has an unflexible way of checking for "null" values, in particular in
primary-/foreign-key fields, that is located in BrokerHelper. For certain
use-cases it must be possible to plug in your own definition of "null",
preferrably through the repository XML-mapping on the "field-descriptor" node.
Example: a table has a single numeric column as primary key, the column is
mapped to a "long" field in Java which is represented internally in OJB as
java.lang.Long. Currently one cannot insert or delte a row in this table where
the primary key is 0, since OJB will throw an exception declaring that all
primary key fields must be non-null.
With the possibility to plug in / change to a more relaxed "null" definition on
this particular PK field, it's possible to work with 0 values for the PK in
this table.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
