Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In XML, it doesn't matter what order the attributes are in. If you have some piece of XML processing code where it does matter, then I would suggest that code was buggy.</p> <p>From the XML spec <a href="http://www.w3.org/TR/2004/REC-xml11-20040204/#NT-Attribute" rel="nofollow noreferrer">here</a>, note the phrase: "Note that the order of attribute specifications in a start-tag or empty-element tag is not significant".</p> <p>In answer to your specific question on whether you can enforce a certain order, I don't believe so. I've never actually tried to do it (since it's unnecessary) but it seems unlikely the REXML people would waste time implementing such a non-feature :-). Since the key/value pairs are stored as a hash, their order is likely to be random (as far as you could tell from the alphabetic sequence of the keys).</p> <p>Of course, since Ruby comes with the source code for REXML, you could (if desperate) replace or augment the included copy with your own version (REXML2 ?).</p> <p>Since you're doing a simple puts, it's probably using the pretty formatter so check the start of the <code>write_element</code> code in <code>src/rexml/formatters/pretty.rb</code> where it performs the "<code>node.attributes.each_attribute do |attr|</code>" - you may find it's as simple as sorting that list before processing the elements.</p> <p>You may also want to suggest to the developers (see <a href="http://www.germane-software.com/software/XML/rexml/index.html#id2248285" rel="nofollow noreferrer">here</a> for the mailing list or <a href="http://trac.germane-software.com//rexml" rel="nofollow noreferrer">here</a> for bug reports and enhancement requests) that they make this an option in a future release but, if I were them, I'd simply say it was unnecessary.</p>
    singulars
    1. This table or related slice is empty.
    1. POREXML preserve attributes order
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USpaxdiablo
    1. USpaxdiablo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POREXML preserve attributes order
      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. COSure, the order does not matter from machine perspective. I need it for readability only. Actually I have to modify config file, and whould like to preserve formatting as much as possible.
      singulars
      1. PO
      1. USalex2k8
    2. COSee updates on possible approaches (basically either forking for local use or trying to convince developers to add this feature).
      singulars
      1. PO
      1. USpaxdiablo
 

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