Databases
StackOverflow2013
Postsdbo
PORuby 1.8.7 ordering of a hash with JSON.parse
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORuby 1.8.7 ordering of a hash with JSON.parse
    primarykey
    data
    text
    <p>I've been having trouble figuring this out so I figured i'd ask here. I'm using Ruby 1.8.7 and RoR 1.2.6. I have my controller rendering this JSON:</p> <pre><code>{ "form_id": "1", "form_structure": { "3": { "answer_required": "undefined", "title": "This is a radio group, right?", "cssClass": "radio", "values": { "4": { "value": "Yes", "baseline": "undefined" }, "5": { "value": "No", "baseline": "undefined" }, "7": { "value": "Maybe", "baseline": "undefined" }, "20": { "value": "Test", "baseline": "undefined" } } } } } </code></pre> <p>As you can see, the options under "values" are ordered by the ID from the table. Looks perfect in JSON. When I use <code>JSON.parse</code> on it, everything under "values" get's all out of whack and it returns this: </p> <pre><code>{ "form_id"=&gt;"1", "form_structure"=&gt;{ "3"=&gt;{ "title"=&gt;"This is a radio group, right?", "cssClass"=&gt;"radio", "answer_required"=&gt;"undefined", "values"=&gt;{ "7"=&gt;{ "baseline"=&gt;"undefined", "value"=&gt;"Maybe" }, "20"=&gt;{ "baseline"=&gt;"undefined", "value"=&gt;"Test" }, "4"=&gt;{ "baseline"=&gt;"undefined", "value"=&gt;"Yes" }, "5"=&gt;{ "baseline"=&gt;"undefined", "value"=&gt;"No" } } } } } </code></pre> <p>This code is used in a formbuilder that I'm making, and it wouldn't really be nice if the form elements that a person builds don't show up in the correct order that they built them in. Anyone have insights on how I can keep the ordering or reorder them as I output or right before then?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAndrew Marshall
    1. USMagicmarkker
    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
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORuby 1.8.7 ordering of a hash with JSON.parse
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThere's no Ruby version 1.8.9…
      singulars
      1. PORuby 1.8.7 ordering of a hash with JSON.parse
      1. USAndrew Marshall
    2. CO`Hash` is not ordered in 1.8.7, can you change your `JSON` so it looks like `{"values" => [[7, {"baseline" => ...}], [20, ...`? It will be a good thing anyway, ordering hash is a tricky business.
      singulars
      1. PORuby 1.8.7 ordering of a hash with JSON.parse
      1. USVictor Moroz
    3. COhash by definition has no order. Deal with it and change it to array.
      singulars
      1. PORuby 1.8.7 ordering of a hash with JSON.parse
      1. USJakub Oboza
 

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