Allow Null - Version 3.5.7-build 520

Classic Servoy
1

Hi to all,
since version 3.5.6, when setting a field as “Row Indent”, the flag “Allow null” was unchecked automatically.
In version 3.5.7 I cannot find a way to uncheck the “allow null” for the Row Indent fields.
Is it a bug ?

Regards,
Riccardo

2

are you sure you use the same context?

like are both in creating a new table in the database?

Because that behavior is different for new or existing tables.

3

Hi Johan,
in my case I don’t create new tables. I use existing tables where the pk is not inherited from the database and I just define the row indent in Servoy.
When deploying a solution based on such tables I’m obliged to repeat manually the row indent settings in the production environment, since these settings are not exported with the solutions.
In 3.5.7 this seems not to work any more.

4

i dont think allownull can be changed for existing tables. That is fixed when you have created a table.
If you want to change that, you have to use the db tooling and alter that column property.

5

I would like to highlight that the behavior of 3.5.7 has change compared to the previous versions (Servoy 4 also works as 3.5.7).
In 3.5.6, working ON EXISTING TABLES AND FIELDS, when setting a fields as “row indent”, the “allow null” is unchecked.

Sincerely I was experting an improvement of the futures related with Row Indent (see my previous issue: http://www.servoy.com/forum/viewtopic.php?f=11&t=10636 ) and not additional restrictions.

The “allow null” as also the pks, defined directly in the db, are not inherited in servoy because the jdbc driver is not complying to the jdbc specification and I cannot change the db to preserve other systems using it (http://www.servoy.com/forum/viewtopic.p … dbc#p41684).

I’m not sure about the impact in setting the “row indent” and leaving not managed the “allow null”, considering that the previous versions didn’t allow such combination.
In my opinion the behavior of 3.5.6 is more safe and proper, since pks (row indent) cannot be null.

6

That allow null was unchecked in 3.5.6 was a bug or wrong representation to you because when you made a row ident on an existing column/table then we cant change the allow null to false because that is database information itself and we
cant set suddenly to a column that the column cant have null values. For this you need to use your own database specific tools.