Given over half of a typical repository is a delta, this is not a bad idea. It will allow you to optimize some of the SQL for delta lookups.
On Mon, 22 Jan 2018 21:04:26 -0500 Richard Hipp <[email protected]> wrote: > On 1/22/18, [email protected] <[email protected]> wrote: > > In rebuild.c (commit 1a95af721e467a6e3321c1557c4f0cdfa353ef4a): > > > > Ln 168: > > > > db_multi_exec( > > "CREATE VIEW IF NOT EXISTS " > > " repository.artifact(rid,rcvid,size,atype,srcid,hash,content) AS " > > " SELECT blob.rid,rcvid,size,1,srcid,uuid,content" > > " FROM blob LEFT JOIN delta ON (blob.rid=delta.rid);" > > ); > > > > It appears that this view is not in use at all. What is this for? > > At one point I was going to try to combine the BLOB and DELTA tables > into a single table named ARTIFACT. This was a stepping stone toward > that goal. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
