| Re: [stellation-res] A database proposal, for fixing 22135. |
On Sun, Aug 04, 2002 at 08:10:13PM -0400, Mark C. Chu-Carroll wrote: [snip] > OK. Enough background. Here's what I'd like to do. > > I'd like to separate the tags from the lines in the database. And I'd > also like to burst the tags out, so that instead of bunding the information > about what versions a given line is part of into a tag string, it gets > broken out into a bunch of lines in a different table. > > So... The Texts table becomes two tables: TextLines, and TextVersions. > Each row in TextLines is an artifactID, and a line ID, and the line string. > > TextVersions is a list of (linenumber, LineID, VersionIDs). There is an > entry in TextVersions for a LineID,VersionID if the line is a member > of the version. There is something that bugs me for a couple of days... Stellation is plugin based: each artifact is [supposed to be] manipulated by a plugin that knows how to parse/merge/diff it. If that't the case, why is the database schema assuming that text files can be _meaningfully_ sliced into lines of text? Shouldn't the stellation core store the artifact data in whatever format it pleases (simple linked list of blobs containing data/delta or files stored at filesystem lever or ...) and serve it to the appropriate plugin as a big chunk'o'bits? florin -- "If it's not broken, let's fix it till it is." 41A9 2BDE 8E11 F1C5 87A6 03EE 34B3 E075 3B90 DFE4
Attachment:
pgpwTh8BgaP5Q.pgp
Description: PGP signature