Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You don't mean thread. JavaScript is single-threaded, so node is single-threaded. I don't mean to be picky, but people will understand you better if you use the nomenclature they've learned. The words 'thread' and 'process' are already too heavility overloaded at the OS level, best to avoid them unless that's really what we mean.</p> <p>It is quite common in node to pass the entire request object around.</p> <p>You have not provided a strong use case for building this identity map. Can you elaborate? </p> <p>If you really need to keep track of individual callbacks, you could use a guid-generator. Of course, you have to store those guids someplace and depending on how you do that you could end up creating a bottleneck for scaling.</p> <p>Ah.. I see your edit now... Where you write "where the App.User query can store it's results (and any other models can store their results, so if they are requested again it doesn't hit the database)." you're already thinking at a very high level. This is less of a node.js question and more of a framework question. What I mean is, node.js is a low-level kit which markets itself as a high-level framework. It's basically a mashup of javascript with an event loop supported by a thread pool. That would be OS threads, by the way. I think the answer to your question may be that you need to explicitly provide caching in your objects if you're looking to avoid extra hits to the database. As far as I know, there's no high-level magic for that baked into node. I know that doesn't really help, except maybe to say don't feel bad about not finding something that isn't there.</p> <p>Re: globals. Just don't do it. Friends don't let their friends write to global. :)</p>
    singulars
    1. This table or related slice is empty.
    1. POAccessing the currently executing "request" or "thread" as if it were global in Node.js?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCarlos
    1. USCarlos
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat do you recommend I call it? I get what you're saying, but for my particular case passing the request all over the place would be undesirable (appended to question). Is there no way to keep track of processes/threads/whatever-theyre-called in Node.js to avoid passing the request around?
      singulars
      1. PO
      1. USLance Pollard
    2. COIt would be nice to know in general how executing code in Node.js is executed, how it jumps between callbacks and such and if it stores some sort of process id or something.
      singulars
      1. PO
      1. USLance Pollard
    3. COI agree that avoiding globals is a good thing. However, globals are, I'd say, one of the major things that made Rails possible (clean api), if you really look at the source code. They are the foundation for making database queries, for example.
      singulars
      1. PO
      1. USLance Pollard
 

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