Change 7198
It is now possible to accumulate output from multiple
invocations of track2sql in a single database. Previously,
the processKey was a incrementing value that always started
at zero. Therefore, processKeys from separate runs of
track2sql would collide if inserted into the same databse.
Now, track2sql uses a 36 character universally unique
identifier (UUID) for each process. UUIDs give us reasonable
confidence that the process keys will never collide.
One consequence of this change is that the schema is
slightly different. The type of the processKey column is
now a 36 character varchar instead of a integer.
Another side-effect of this change is that the output of
track2sql cannot be predicted and will always be different
even when processing the same log file.
Track2sql performance is largely unaffected, however, insert
and select performance may degrade somewhat due to the
larger key size.
invocations of track2sql in a single database. Previously,
the processKey was a incrementing value that always started
at zero. Therefore, processKeys from separate runs of
track2sql would collide if inserted into the same databse.
Now, track2sql uses a 36 character universally unique
identifier (UUID) for each process. UUIDs give us reasonable
confidence that the process keys will never collide.
One consequence of this change is that the schema is
slightly different. The type of the processKey column is
now a 36 character varchar instead of a integer.
Another side-effect of this change is that the output of
track2sql cannot be predicted and will always be different
even when processing the same log file.
Track2sql performance is largely unaffected, however, insert
and select performance may degrade somewhat due to the
larger key size.