On 5/24/21 2:17 PM, Martin Simmons wrote:
>>>>>> On Fri, 21 May 2021 21:21:43 -0400, Phil Stracchino said:
>> Actually upon consideration of the shape of the curve I went with
>> VARBINARY(80).  I'll be surprised if I ever see an LStat with length 75.
> 
> I have some with length 76.  But does it make any difference?  I would expect
> the data storage size to be the same for any VARBINARY below something like
> 255.

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.

>> What is Job.PriorJob used for?  I have 486 rows currently in Job; in 480
>> of them, including the 68 rows in which PriorJobId is non-zero, PriorJob
>> is NULL, while in the remaining six rows it is an empty string.  Is it
>> even used?
> 
> It seems to be new in version 11 and contains the Job.Job of the original Job
> in a Migration or Copy job.  It is returned by the function
> BDB::bdb_find_job_start_time in src/cats/sql_find.c, where there is also a
> comment about it.


Ah, so...



-- 
  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

Reply via email to