+1 to fix + note in the migration guide.
On Fri, Nov 2, 2018 at 8:29 AM Guillaume Smet
wrote:
> Yeah, personally, I think it's a bug, e.g. this type shouldn't have been
> used in the first place.
>
> But as it works when not storing nulls in the column, YMMV depending if you
> use null or not.
Yeah, personally, I think it's a bug, e.g. this type shouldn't have been
used in the first place.
But as it works when not storing nulls in the column, YMMV depending if you
use null or not.
My vote goes to fix + note in the migration guide.
Gail, what's your take on this one?
Thanks!
On
In the general sense, it ultimately comes down to how one views the
situation. Is it a bug? Then I think it is reasonable to just change it
and mention it in the migration guide. If it is an enhancement, then I
think a setting makes sense to control this.
Honestly though, not sure this has a
Hi,
Quite some time ago, someone opened
https://hibernate.atlassian.net/browse/HHH-12850 stating that null values
were not supported for Booleans with SAP SQL Anywhere.
This is due to the fact that null values are not supported for bits and we
should use a tinyint. Interestingly enough, it was
