Uninitialized booleans in Data Tables

I set up my first data table which had a number of booleans in it. When I queried it with the following code

cards = app_tables.card_info.search(blank_back=False)

No rows were returned. However if I changed the input to True, I got the expected rows.
I then went to the data table and clicked on and off the checkbox for each of the rows that were False. I reran the first query and now got the expected results instead of no rows.

I then saw there was and ‘auto create missing columns when adding rows option’ so I checked that. I then added a new row with blank_back = False and it didn’t show up.

I take it that there are 3 possible values for a boolean, True, False, and Null? If so is there any way to set up a default value when manually entering information to the data tables through the UI?

Thanks

The initial value is “None”.
I think this is a bug for a column that is meant to be True or False.

I vote for it being False on creation through the IDE if we can’t set default values ourselves.

Having the options to

  • Set default values (incl. None)
  • Set constraints

(where applicable) would go a long way towards helping ensure classical “relational integrity”.

1 Like

2 posts were split to a new topic: Boolean columns neither True, False nor None

Default value should be False, and allow override to None on a column-by-column basis. None value is a surprise on a True/False column.