Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is my attempt... What I don't really "get" about my attempt is whether it's 100% safe or not.</p> <p>If <code>store.add()</code> is called twice in a row, is is ever possible that <code>inMethod</code> is set to <code>true</code> by the first call, and that the second <code>add()</code> call then finds it already set to true because the first one hasn't managed to set it to false yet?</p> <p>This would only really be possible if <code>nextTick()</code> is called in between the two calls I assume?</p> <p>Or am I just completely confused by it all? (Which is very possible...)</p> <pre><code> topic.subscribe( 'hotplate/hotDojoStores/newStore', function( storeName, store ){ var inMethod; aspect.around( store, 'put', function( put ){ return function( object, options ){ if( inMethod ){ return when( put.call( store, object, options ) ); } else { inMethod = true; try { return when( put.call( store, object, options ) ).then( function( r ) { var eventName; var identity = store.idProperty; eventName = object[ identity ] ? 'storeRecordUpdate' : 'storeRecordCreate'; topic.publish( eventName, null, { type: eventName, storeName: storeName, objectId: r[ identity ], object: object }, false ); }); } finally { inMethod = false; } } } }); aspect.around( store, 'add', function( add ){ return function( object, options ){ if( inMethod ){ return when( add.call( store, object, options ) ); } else { inMethod = true; try { return when( add.call( store, object, options ) ).then( function( r ) { var identity = store.idProperty; topic.publish('storeRecordCreate', null, { type: 'storeRecordCreate', storeName: storeName, objectId: r[identity], object: object }, false ); }); } finally { inMethod = false; } } } }); aspect.around( store, 'remove', function( remove ){ return function( objectId, options ){ return when( remove.call( store, objectId, options ) ).then( function( r ) { topic.publish('storeRecordRemove', null, { type: 'storeRecordRemove', storeName: storeName, objectId: objectId }, false ); }); }; }); }); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUsing aspect.around, but checking for methods calling each other
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMerc
    1. USMerc
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsing aspect.around, but checking for methods calling each other
      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. VTAcceptedByOriginator
    1. COIf the two add() are back to back, they're in the same stack & therefore same event loop: so they won't get interleaved. The return in your try cannot complete until the promise resolves (because of the .then), so that will prevent Promise stacking. So while the code seems safe, why not refactor to the whenFinished() pattern established by Observable? From what I can tell, the only extension is publishing a topic after the method concludes.
      singulars
      1. PO
      1. USbishop
    2. COWell it's about using Dojo, rather than inventing the wheel... Dojo provides `aspects`. So, why not use them, really? I think Observable does it "by hand" because it's old code... Plus, I might well need to put things "around" later on in my code.
      singulars
      1. PO
      1. USMerc
    3. COSure, ok. I'm just thinking that if the code looks worrisome it probably is in subtle ways that even a pair of eyes may miss. So how about Aspect.after() and a duplicate suppression filter on topic.publish?
      singulars
      1. PO
      1. USbishop
 

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