-
Notifications
You must be signed in to change notification settings - Fork 936
Description
I recently updated from 5.2 to 5.3 and my application started crashing depending on whether you continued of existing files or started fresh.
The reason being that I had a SQL query that accesses a single record and a single column, that ended with .UniqueResult<bool>
. With old files created with NHibernate 5.2 the result from the preceding code is a object { bool }
but with fresh files from NHibernate 5.3 it became a object { long }
.
Seeing that users can either continue off their existing files or that new users create fresh files, I now have to take this underlying (breaking) change into account that it can be either a long
or a bool
.
It seems that the SQLite columns for fresh files are now integers
, while for the old one they are boolean
, but I did not find any mention of this in the changelog.
The fact that this particular one breaks is only a small part of my concern that this could influence all the code that somewhere have an underlying bool.
I did not find this change in the changelog or any migration guidelines, so I'm not sure how I should handle this.
Note: I make use of class mappings that contains some booleans (one of which i'm using in the query above).