Re: Bacula 15.0.2 update

On 5/10/24 14:01, Martin Simmons wrote:
> But I think you are mixing two different concepts: in CREATE TABLE, a DEFAULT
> just specifies what INSERT does if the column is omitted; NOT NULL is a
> constraint that applies all the time.  It is quite reasonable to specify NOT
> NULL for a column that must always be given a value in an INSERT statement.


Oh yes, absolutely.  That's its *purpose*.  "Column is not allowed to be 
NULL."  Where thew problem can arise is if you don't supply a value for 
a column that you've told the DB is not allowed to be NULL, but you 
haven't given it an explicit DEFAULT to use if you don't supply a value, 
and you're in STRICT mode so the DB won't fill in an *implicit* default.

What happens then is that the DB throws an error on the query — which is 
probably what you *want* to happen.



-- 
   Phil Stracchino
   Fenian House Publishing
   [email protected]
   [email protected]
   Landline: +1.603.293.8485
   Mobile:   +1.603.998.6958



_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel