Navicat responded that when empty is not specified that null is the SQL92 default. This is correct although I am not sure that in-table editing is covered in any version of the SQL standard. I responded that all other GUIs that I have used switch the default to empty when the column is defined as not null. This was passed onto their develpment team as a feature request, but is still not there. Technically, Navicat are correct, even when a table is defined as not null, it is the users' responsibility to not enter any nulls. The problem with in-table editing is that you cannot enter a field as empty unless you change all your column defaults to empty. Little wonder that Postgres' manual regards default to null as a mistake in the standard. Nulls have their uses but are generally a pain (e.g., for column sorting, boolean logic and concatenaed fields).
Existing users, log in. New users, create a free account. Lost password?
Navicat's approach is correct, but ... - McClie
Navicat responded that when empty is not specified that null is the SQL92 default. This is correct although I am not sure that in-table editing is covered in any version of the SQL standard. I responded that all other GUIs that I have used switch the default to empty when the column is defined as not null. This was passed onto their develpment team as a feature request, but is still not there. Technically, Navicat are correct, even when a table is defined as not null, it is the users' responsibility to not enter any nulls. The problem with in-table editing is that you cannot enter a field as empty unless you change all your column defaults to empty. Little wonder that Postgres' manual regards default to null as a mistake in the standard. Nulls have their uses but are generally a pain (e.g., for column sorting, boolean logic and concatenaed fields).Reply to This
Thursday, April 06 2006 @ 04:52 PM PDT