Eureka!

  1.  
    1. Aug 7, 2007
      szaijan says:

      That did it. You'd think I'd have seen that, but I suppose I stared too long and hard. Many thanks, crism!

      2.
        Aug 7, 2007
        szaijan says:

        Oh, the final query looked like:

        {
        "query":{
        "id":"#9202a8c04000641f800000000031e51b",
        "type":{
        "connect":"insert",
        "id":"/user/szaijan/fantasy_football/player",
        "type":"/type/type"
        }
        }
        }

        And had this result:

        {
        "code":"/api/status/ok",
        "result":{
        "id":"#9202a8c04000641f800000000031e51b",
        "type":{
        "connect":"inserted",
        "id":"/user/szaijan/fantasy_football/player",
        "type":"/type/type"
        }
        }
        }

        Now, is there a way to order the inserts in my query such that I can do the above first, and then fill in any player fields I care to once the type is added, but in a single query I'm guessing not, but it would be handy. I'll experiment.

      3. alexander
        Aug 7, 2007
        alexander says:

        As long as you fully qualify the property names ("/user/szaijan/fantasy_football/player/position" for example), you can add the properties in the same query, and the order doesn't matter.


    Discussion is posted in:

    Think this discussion also relates to something else? Cross-post it by adding a new discussion area:

Related Discussions