On 5/26/21 3:22 AM, Eric Bollengier via Bacula-devel wrote: > Hello, > > On 5/25/21 18:14, Phil Stracchino wrote: >> Well, true, yes. VARCHAR(80) doesn't actually save anything over >> VARCHAR(96) unless there are values over 80 characters. Good point. I >> suppose for prudence' sake 96 or even 128 would be safer. > > I would recommend to not change this parameter, the LStat field size can vary > from one platform to an other (on windows or FreeBSD, it is longer than on > Linux). > We may need to encode any kind of data into the field to get it back at the > restore time and during the file selection.
How MUCH longer? TEXT fields are really a bad idea. Is there no safe "never exceed" number that we can decide on? As a database architect my instinct is to keep fields as short as possible, but the incremental cost of increasing the maximum size of a VARCHAR or VARBINARY field is very small. We're really using far too many TEXT and BLOB columns, and most of them are in places where they're not necessary or even appropriate. (A BLOB for an md5sum?) -- Phil Stracchino Babylon Communications 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
