Databases
StackOverflow2013
Usersdbo
USPatrick Karcher
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USPatrick Karcher
    primarykey
    data
    text
    plurals
    1. POLinq to DataTable without enumerating fields
      singulars
      1. PTQuestion
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMemory usage, SortedList vs List problem
      1. USPatrick Karcher
      1. VTFavorite
    2. VO
      singulars
      1. POLinq Query To Combine 2 Lists
      1. USPatrick Karcher
      1. VTFavorite
    3. VO
      singulars
      1. POWill the Garbage Collector call IDisposable.Dispose for me?
      1. USPatrick Karcher
      1. VTFavorite
    1. COYes, that is the advantage that constraints give you. (1) As with any good practice, evaluate how important it is in the particular situation. (2) Balance the ROI of doing this good practice compared to the others, with limited time. (3) Consider whether the good practice in question, despite any advantages it brings, can be a **crutch** that allows the developers to think they can **avoid** other good practices, which might actually be more important. In multiple instances I've seen good DB design/nomenclature take 2nd place to constraints. Disaster. The reverse, usually not as bad.
      singulars
      1. PO
      1. USPatrick Karcher
    2. CO@Henk: Dispose() is not called by GC, right? Now, making the GC deal with a finalizer method has overhead (and can make object stay around longer), but might it not be worth it to make sure an important Dispose method gets called? To me it seems like a judgement call. Let's say an object BigShot is long-lived anyway, and has referenced to many LittleShot (implementing IDisposable) objects whose unmanaged resources are known to really need clean-up. Shouldn't we weigh creating a BigShot finalizer against making sure all those resources are cleaned up? It seems like a judgement call to me.
      singulars
      1. PO
      1. USPatrick Karcher
    3. COI think sargable is the next step. We don't know enough about the conditions to suggest an optimal strategy, or even if the scale warrants any such effort.
      singulars
      1. PO
      1. USPatrick Karcher
 

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