On 5/10/24 07:40, Martin Simmons wrote:
On Thu, 9 May 2024 14:45:31 -0400, Phil Stracchino said:
It is an INT UNSIGNED NOT NULL (with no DEFAULT specified) in FileMedia,
but it is a signed INT(11) in every other table where it exists. It is
inconsistently allowed to be NULL, has a DEFAULT specified in BaseFiles
but is allowed to be NULL there, is NOT NULL DEFAULT 0 in Object but
NULL DEFAULT 0 in RestoreObject, ...
Is this column *SUPPOSED* to be INT UNSIGNED NOT NULL DEFAULT 0 wherever
it exists?
No, FileIndex is signed in the File table at least (-ve is used to mark
deleted files in an accurate backup).
Then should it not be signed *everywhere*? Or are these just a group of
disparate columns not used outside their tables that just HAPPEN to all
have the same name?
And should it be allowed to be NULLable?
--
Phil Stracchino
Fenian House Publishing
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
