You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Thomas Fox (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/04/14 17:07:16 UTC
[jira] [Issue Comment Edited] (TORQUE-186) BOOLEANINT and null
value
[ https://issues.apache.org/jira/browse/TORQUE-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254135#comment-13254135 ]
Thomas Fox edited comment on TORQUE-186 at 4/14/12 3:06 PM:
------------------------------------------------------------
The expected behaviour is equal to the behaviour in Torque 3.3
was (Author: tfischer):
The expected behaviour is ewuatl to the behaviour in Torque 3.3
> BOOLEANINT and null value
> -------------------------
>
> Key: TORQUE-186
> URL: https://issues.apache.org/jira/browse/TORQUE-186
> Project: Torque
> Issue Type: Bug
> Reporter: Thomas Fox
> Assignee: Thomas Fox
>
> In the current 4.0 SNAPSHOT, I have a BOOLEANINT object column which is mapped to a java Boolean object.
> Currently, the database value null is mapped to Boolean.False and the java value null is mapped to 0 in the database
> Expected behaviour:
> The database value null is mapped to java null and the java value null is mapped to null in the database.
> It remains to be checked what the behaviour for Torque 3.3 is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org