[ http://216.121.112.228/browse/NH-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo closed NH-2667.
---------------------------
Resolution: Won't Fix
The Version can be null or you have to use the "unsaved-value".
Your legacy DB should have consistent data.
> Version properties which are NULL in the database cause exceptions during a delete or update
> --------------------------------------------------------------------------------------------
>
> Key: NH-2667
> URL: http://216.121.112.228/browse/NH-2667
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.1.2.GA, 3.0.0.Alpha1, 3.0.0.Alpha2, 3.0.0.Alpha3, 3.0.0.Beta1, 3.0.0.Beta2, 3.0.0.CR1, 3.0.0.GA, 3.1.0, 3.2.0Alpha1, 3.2.0Alpha2
> Reporter: Mike Pontillo
>
> I have a legacy database application which NHibernate must operate side-by-side with, against the same database.
> The legacy application sometimes adds NULL values to version columns. When trying to delete or update such a row, NHibernate throws exceptions. The original issue was documented here:
> http://groups.google.com/group/nhusers/browse_thread/thread/637c7e2bf68b7f17/8b9115bd53edfb99?#8b9115bd53edfb99
> Patch with test cases to follow shortly.
> I also have a patch with a tentative fix, but it may need some additional discussion before it is applied.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
