Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Actually I would mix both metadata in svn properties and (versioned) plain xml-like files.</p> <p>1) Everything that is related to the server can conveniently be stored in svn properties, if you need that which might not be the case here. I mean properties to do something special about a file or a directory when you proceed to commits, checkouts/exports, ... For example if you want to use the hook scripts to update some external documentation each time you touch a particular file.</p> <p>Using hook scripts like that to maintain separate information up-to-date usually avoids more time-consuming procedures that scan the whole database, it is less heavier for the server.</p> <p>2) Scripts to process your database would have a better place in repository files (xml, or whatever you feel most at ease with). A typical example is a script that compiles everything or part of your tools and builds an installer, storing specifics about your tools in an easily readable/manageable file makes sense. And as you pointed out, it has to be server-independent as much as possible (yet you could have some links like including the revision in the final application to keep track of their versions).</p> <p>It is how I proceed now, and it works well (not much elaborated on the hook scripts yet though). It helped to separate both.</p> <p>I'm just not convinced yet what the best language would be to implement hook scripts. Python (with <a href="http://pysvn.tigris.org/" rel="nofollow noreferrer">pysvn</a>) is great but forces a reload of the interpreter each time and is dynamically typed - haven't checked the impact. I couldn't find yet any reliable API for C# that would also work on Linux with Mono, maybe C or C++. It mostly depends what has to be done I suppose.</p>
    singulars
    1. This table or related slice is empty.
    1. POmetadata for subprojects within an svn repository
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRedGlyph
    1. USRedGlyph
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      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