I get a warning, that: “row identifiers should always be not null”, but I can’t deactivate the “Allow Null” checkbox for a table’s “Row Ident”. In the FoxPro DBF table “Allow null” is not activated.
[attachment=0]2014-03-06_10_29_24-Servoy_Developer_table_allow_null.png[/attachment]
What did you mean by ‘In the FoxPro DBF table “Allow null” is not activated.’? Can you give a screen-shot of that?
You expect “Allow null” to show unchecked in table editor for that column, right?
That’s just a warning dialog, I remember it was added to not completely disallow adding ‘dbident’ to old DBF tables - that had records in them, allowed null but had no null values in that column.
So as long as your table has non-null data in that column in all records, it should work as expected. The purpose of that dialog is to make you aware of this requirement.
Andrei Costescu:
What did you mean by ‘In the FoxPro DBF table “Allow null” is not activated.’? Can you give a screen-shot of that?
[attachment=0]2014-03-06_12_33_08-FoxPro_Table_Designer_no_null_allowed.dbf.png[/attachment]
I think “Allow null” was not the right expression in the FoxPro context. Sorry
Andrei Costescu:
You expect “Allow null” to show unchecked in table editor for that column, right?
I exspect, that can deactivate the “Allow Null” for the “Row Ident” column in Servoy, so that I get no warning, because the row identifier is generated by Servoy.
Andrei Costescu:
That’s just a warning dialog, I remember it was added to not completely disallow adding ‘dbident’ to old DBF tables - that had records in them, allowed null but had no null values in that column.
So as long as your table has non-null data in that column in all records, it should work as expected. The purpose of that dialog is to make you aware of this requirement.
But if I have a Servoy generated “Row Ident”, it is not required to show a warning, if it would be possible to deactivate “Allow Null”?
Same issue here. Did you solve your problem in the meantime?
ina.wels:
Same issue here. Did you solve your problem in the meantime?
Hello Ina, no I didn’t solved it.
I think you should create a case about this. Either the driver doesn’t provide that “non-nullable” info from the driver or it’s not interpreted correctly.
I guess if you do an insert query with null value for that column or without giving a value when NULL mode is enabled it will fail.
