Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>To my knowledge, there are no standards for passing structured data using GET. There are a handful of conventions (the PHP/RoR example above possibly the most prevalent), but nothing that has reached any level of maturity, documentation, reference implementation etc... to be considered a standard.</p> <p>And it's not too surprising a simple standard hasn't emerged. There are open questions whose answers depend upon specifics of the situation. Should the URL be transparent (as visible query parameters) or opaque (e.g. base64 encoded). Can compression be used? Can/should/must other representations be used/supported, e.g. JSON, binary XML or even Google's <a href="http://code.google.com/apis/protocolbuffers/" rel="nofollow noreferrer">protocol buffers</a>). How is URL overflow handled? 10 different people might all give different answers about what needed based on their situation. A standard could attempt to address all these concerns, but it would then be far from simple.</p> <p>Even if there were a standard, would it make sense to follow it?</p> <p>It's desirable, comforting even, to follow a standard, knowing that your work is building on the road-tested work of respected field-experts and engineers, and knowing that we are invited to the party and play with other systems that follow the same standard. But when the requiremtents are diverse, as they are here, a standard will typically only give you a middle-ground solution, a medium of comprimise. And when you've only got <a href="https://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-an-url">2K</a> to play with, comprimising is probably last on your list!</p> <p>Roll your own and you'll be sure to get exactly what you want. I'd go for representing as binary XML or protocol buffers, gzipped and base64 encoded, but you're millage may vary.</p> <p>Either way, good luck!</p>
    singulars
    1. This table or related slice is empty.
    1. POIs there a standard syntax for encoding structure objects as HTTP GET request parameters?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USmdma
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs there a standard syntax for encoding structure objects as HTTP GET request parameters?
      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. VTBountyClose
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThis is the conclusion I've come to as well. We're on our way already.
      singulars
      1. PO
      1. USlexicore
 

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