Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In <a href="http://rads.stackoverflow.com/amzn/click/0321356683" rel="noreferrer">Effective Java, 2nd edition</a>, Joshua Bloch certainly recommends the former. There are a few reasons I can remember, and doubtless some I can't:</p> <ul> <li>You can give the method a meaningful name. If you've got two ways of constructing an instance both of which take an int, but have different meanings for that int, using a normal method makes the calling code much more readable.</li> <li>A corollary of the first - you can have different factory methods with the same parameter list</li> <li>You can return null for "potentially expected failure" cases whereas a constructor will <em>always</em> either return a value or throw an exception</li> <li>You can return a type other than the declared (e.g. return a derived class)</li> <li>You can use it as a factory, to potentially return a reference to the same object several times</li> </ul> <p>The downsides:</p> <ul> <li>It's not as idiomatic, currently - developers are more used to seeing "new"</li> <li>If you see "new" you <em>know</em> you're getting a new instance (modulo the <a href="https://stackoverflow.com/questions/194484/whats-the-strangest-corner-case-youve-seen-in-c-or-net">oddity I mentioned recently</a>)</li> <li>You need to make appropriate constructors available for subclasses</li> <li>In C# 3, constructor calls are able to set fields/properties in a compact manner with object initializer expressions; the feature doesn't apply to static method calls</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POStatic factory methods vs Instance (normal) constructors?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USJon Skeet
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POStatic factory methods vs Instance (normal) constructors?
      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. COReading Item 2 in Effective Java one can easily get the impression that Joshua Bloch is in favour of using static factory methods as the default choice. But I don't think that's actually the case, or at least it wasn't in 2002 when he did [this interview](http://www.artima.com/intv/bloch14.html) with Bill Venners that I quoted in my answer further down.
      singulars
      1. PO
      1. USMB.
    2. COre. your point about c#, I've used this pattern in the past; See my answer here which offers a workaround to the compact initializer problem (well, replaces it with something which is also compact anyway!) http://stackoverflow.com/a/10171659/705589
      singulars
      1. PO
      1. USMikey Hogarth
 

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