Ultralite 17 is allowing nulls in a not null column

[former_SQLA_member1694899]

HI, I'm running a UWP app against an ultralite version 17 database on Windows 10 Mobile Enterprise.

We've had replication fail because the column value in the ultralite database was null even though it's defined to be not null.

How could this be happening? If I try to manually insert a null value, it does not work, of course. But somehow with the application the database is accepting a null value. The column in question is a BLOB/long binary and is used to hold images, if that makes a difference.

Is there any logging I can turn on for the UL database?

Thanks, Paula

[former_SQLA_member1694876]

Hi Paula,

Is this something you can reproduce?

Can you show the log from MobiLink where the error is reported?

[chris_keating]

DO you know if this value was originally from an INSERT or as part of a synchronization? Is this reproducible or a single occurrence? Have you checked the health of the database with ulvalid?

[former_SQLA_member1694884]

What is your consolidated? Some databases don't distinguish between empty strings and null strings, so an empty string in UL might be interpreted as a null value in the consolidated. I'm not sure if that applies to blob values, though.

Are you using the direct row API to generate the download?