Databases
StackOverflow2013
Postsdbo
POmetadata for subprojects within an svn repository
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POmetadata for subprojects within an svn repository
    primarykey
    data
    text
    <p>Basically I'm looking for a way to find things more easily within a large/complex SVN repository.</p> <p>(I frequently work on small tool applications, and will be shortly moving them into a common SVN repository. So I'm thinking of the case where may be dozens or even hundreds of little tool applications in one place. I've got a dozen or two and already I lose track sometimes of where I used some particular feature or library or build technique, or even which tool does what.)</p> <p><strong>Has anyone made a lot of use with metadata in an svn repository? What's worked and what hasn't?</strong></p> <p>I'm talking not only of how to store metadata, but what you do with it, like generating an HTML index. For storage, the way I see it there are 3 basic possibilities:</p> <ol> <li><p><strong>put your metadata in a plain file that is checked into the svn repository.</strong> (e.g. some xml file with a special file convention e.g. svn-metadata.xml) This will then be versioned, but it makes it independent of svn.</p></li> <li><p><strong>use svn properties to store metadata.</strong> (works ok, and is versioned, but then you are tied to svn. Plus side is that you can tie metadata specifically to individual files.)</p></li> <li><p><strong>store metadata in an external location</strong> like a database or a wiki. (integrates more directly that storage location's features, but wouldn't be versioned, and is tied to that kind of storage.)</p></li> </ol> <p>I'm thinking of maybe using RDF + RSS as metadata in a plain file, and then writing something that periodically scans the SVN repositories for metadata, indexes it in a database, and generates an easy-to-use web app to make it easier to find.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJason S
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POmetadata for subprojects within an svn repository
      1. USRedGlyph
      1. VTFavorite
    2. VO
      singulars
      1. POmetadata for subprojects within an svn repository
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POmetadata for subprojects within an svn repository
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload