Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think that a good way to answer this question would to approach it from the other side. What practices make XSLT <em>ineffective</em>, and why?</p> <p>Some of the things that I've seen that result in ineffective XSLT:</p> <ol> <li><p><strong>Overuse of <code>for-each</code>.</strong> Everyone's said it; I'm saying it again. I find that <code>for-each</code> is often a sign of the developer trying to employ traditional programming techniques in a declarative language.</p></li> <li><p><strong>Underutilizing XPath.</strong> A lot of bad XSLT I've seen exists purely because the developer didn't understand predicates, axis specifiers, <code>position()</code>, and <code>current()</code>, and so he implemented logic using XSLT constructs instead.</p></li> <li><p><strong>Underutilizing metadata.</strong> You can sometimes eliminate an <em>enormous</em> amount of XSLT by providing your transform with metadata. </p></li> <li><p><strong>Underutilizing pre-processing.</strong> If, for instance, an XML document contains data that has to be parsed using XSLT string manipulation, it's often much simpler to do all of the parsing outside of XSLT and either add the parsed results to the XML or pass the parsed results as an argument to the transform. I've seen some remarkably unmaintainable XSLT implementing business logic that would be trivial to implement in C# or Python. </p></li> </ol> <p>The biggest problem that I'm running into in my own XSLT world (I have several 3,000+ line transforms that I'm maintaining) is dead code. I'm certain that there are templates in my transforms that will never be used again, because the conditions they're testing for will never arise again. There's no way to determine programmatically if something like <code>&lt;xsl:template match="SomeField[contains(., "some value")]&gt;</code> is alive or dead, because it's contingent on something that metadata can't tell you.</p>
    singulars
    1. This table or related slice is empty.
    1. POWriting effective XSLT
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRobert Rossney
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWriting effective XSLT
      singulars
      1. PTQuestion
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COHi Robert, one way to minimize dead code is to use a library of functions/templates, such as FXSL. Then probably, you'd never have to write a 3000+ line transformation. One of the most comlex stylesheet I have ever written -- a parser for XPath 2.0 is just 657 lines. Of course, many FXSL funcs. used
      singulars
      1. PO
      1. USDimitre Novatchev
    2. COI do use template libraries. The problem I'm having is different. If I stop using the "Foo" element in my XML, nothing tells me to remove its matching template from my XSLT.
      singulars
      1. PO
      1. USRobert Rossney
 

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