Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't think so, necessarily. IDisposable technically <i>is</i> meant to be used for things that have non-managed resources, but then the using directive is just a neat way of implementing a common pattern of <code>try .. finally { dispose }</code>.</p> <p>A purist would argue 'yes - it's abusive', and in the purist sense it is; but most of us do not code from a purist perspective, but from a semi-artistic one. Using the 'using' construct in this way is quite artistic indeed, in my opinion.</p> <p>You should probably stick another interface on top of IDisposable to push it a bit further away, explaining to other developers why that interface implies IDisposable.</p> <p>There are lots of other alternatives to doing this but, ultimately, I can't think of any that will be as neat as this, so go for it!</p>
    singulars
    1. This table or related slice is empty.
    1. POIs it abusive to use IDisposable and "using" as a means for getting "scoped behavior" for exception safety?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAndras Zoltan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs it abusive to use IDisposable and "using" as a means for getting "scoped behavior" for exception safety?
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI believe it is an artistic use of "using" as well. I think that Samual Jack's post linking to a comment from Eric Gunnerson validates this implementation of "using". I can see excellent points made from both Andras and Eric on this.
      singulars
      1. PO
      1. USIAbstract
    2. COI talked to Eric Gunnerson about this a while back and according to him, it was the intention of the C# design team that using would denote scopes. In fact, he postulated that had they designed using before the lock statement, there might not even be a lock statement. It would have been a using block w/ a Monitor call or something. UPDATE: Just realized the next answer is by Eric Lippert who is also on the languages team. ;) Perhaps the C# team itself is not in full agreement about this? The context of my discussion w/ Gunnerson was the TimedLock class: http://bit.ly/lKugIO
      singulars
      1. PO
      1. USHaacked
    3. CO@Haacked - Amusing isn't it; your comment totally proves my point; that you'd spoken to one guy on the team and he was all for it; then pointing out Eric Lippert below, from the same team disagrees. From my point of view; C# provides a keyword that exploits an interface and also happens to yield a nice looking code pattern that works in so many scenarios. If we're not supposed to abuse it, then C# should find another way to enforce that. Either way, the designers probably need to get their ducks in a row here! In the meantime: `using(Html.BeginForm())` sir? don't mind if I do sir! :)
      singulars
      1. PO
      1. USAndras Zoltan
 

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