StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20851196
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-12-31T03:14:43.450
FavoriteCount
0
LastActivityDate
2013-12-31T04:22:01.653
LastEditDate
2013-12-31T04:22:01.653
LastEditorUserId
1748400
OwnerUserId
1748400
ParentId
20847311
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> "is it possible to cancel a request?" </blockquote> <code>HTTP.call()</code> does not appear to return an object on which we could call something like a <code>stop()</code> method. Perhaps a solution would be to prevent execution of your callback based on a <code>Session</code> variable? <pre class="lang-js prettyprint-override"><code>HTTP.call("GET", url, function(error, result) { if (!Session.get("stopHTTP")) { // Callback code here } }); </code></pre> Then when you reach a point where you want to cancel the request, do this: <pre class="lang-js prettyprint-override"><code>Session.set("stopHTTP", true); </code></pre> On the server, instead of <code>Session</code> perhaps you could use an <a href="https://www.eventedmind.com/feed/49CkbYeyKoa7MyH5R" rel="nofollow">environment variable</a>? Note that the <code>HTTP.call()</code> options object does accept a <code>timeout</code> key, so if you're just worried about the request never timing out, you can set this to whatever millisecond integer you want. <blockquote> "is it possible to have multiple query parameters which share the same key?" </blockquote> Yes, this appears to be possible. Here's a simple test I used: Meteor code: <pre class="lang-js prettyprint-override"><code>HTTP.call("GET", "http://localhost:1337", { query: "id=foo&id=bar" }, function(error, result) { // ... }); </code></pre> Separate Node.js server: (just the basic example on the Node.js homepage, with a <code>console.log</code> line to output the request URL with query string) <pre class="lang-js prettyprint-override"><code>var http = require('http'); http.createServer(function(req, res) { console.log(req.url); // Here I log the request URL, with the query string res.writeHead(200, { 'Content-Type': 'text/plain' }); res.end('Hello World\n'); }).listen(1337, '127.0.0.1'); console.log('Server running at http://127.0.0.1:1337/'); </code></pre> When the Meteor server is run, the Node.js server logged: <pre><code>/?id=foo&id=bar </code></pre> Of course, this is only for GET URL query parameters. If you need to do this for POST params, perhaps you could store the separate values as a serialized array string with <code>EJSON.stringify</code>?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMeteor http calls limitations
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsbking
UserOwnerUserId
1. USsbking
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMeteor http calls limitations
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.