On 01/03/18 03:50, John Nemeth wrote: > I did my initial testing of Bacula using sqlite3. I ran into > this problem while switching databases in order to move to production. > Another comment in the script says that one is on their own if they > mess with the schema, which is a fair comment. So, I was wondering > if anybody had any comments on the idea of changing BLOB to VARCJHAR?
Speaking as a long-time MySQL DBA, excessive use of BLOB/TEXT columns is a bad practice in any case. They should be used only when strictly required, because the MySQL MEMORY storage engine does not support BLOB/TEXT types, which means that every temporary table containing a BLOB/TEXT column will be forced to disk, seriously impacting performance. Case-insensitive sorting is NOT a good use case for TEXT/BLOB. Any time you have multiple core tables containing multiple BLOB columns, you should probably re-examine your schema design. BTW, you can also declare the column as VARBINARY(255) NOT NULL which is equivalernt and a little more concise. (And I'd be prepared to bet that for most such columns, 255 characters is anywhere from moderately to grossly excessive.) -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
