db "optimizations" fsvo "optimization"

stop the voodoo with home-rolled "auto increment" type stuff.

also, use sqlite "extensions" for conflict resolution (in schema for
all but the source package table, which has it in saveSourcePackage),
so that we don't need to check for pre-existing records.  the "OR REPLACE"
was doing this previously, but had wierd effects with modifying the
primary key, which would cause db inconsistency and *really* wierd effects
when combined with the triggers).

0 files changed, 0 insertions, 0 deletions