Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What about generics?</p> <pre><code>public class BaseFoo&lt;TDerived&gt; where TDerived : BaseFoo&lt;TDerived&gt; { private bool _myProp = false; public TDerived SetMyProperty() { this._myProp = true; return (TDerived)this; } } public class DerivedFoo : BaseFoo&lt;DerivedFoo&gt; { public bool _derivedProp = false; public DerivedFoo SetDerivedPropery() { this._derivedProp = true; return this; } } </code></pre> <p><strong>But I really think that the coupling between the different levels of the inheritance hierarchy is a big design problem.</strong><br> I suggest you have a look at other fluent interfaces like Fluent NHibernate, Rhino Mocks etc, to see how the "big" guys do it ;-)</p> <p>You could also use extension methods like this, sort of an <em>fluent upgrade</em>. This seems cleaner to me.</p> <pre><code>public static class FooFluentExtensions { public static T SetMyProperty&lt;T&gt;(this T foo) where T : BaseFoo { foo.MyProp = true; return foo; } public static T SetDerivedPropery&lt;T&gt;(this T foo) where T : DerivedFoo { foo.DerivedProp = true; return foo; } } static void Main() { DerivedFoo foo = new DerivedFoo(); // works, because SetMyProperty returns DerivedFoo foo.SetMyProperty().SetDerivedPropery(); BaseFoo baseFoo = new BaseFoo(); baseFoo.SetMyProperty(); // doesn't work (and that's correct), because SetMyProperty returns BaseFoo // baseFoo.SetMyProperty().SetDerivedPropery(); } </code></pre> <p>You could encapsulate every method that you want to be fluent.</p>
    singulars
    1. This table or related slice is empty.
    1. POC# - polymorphism question
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDaniel Hilgarth
    1. USDaniel Hilgarth
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POC# - polymorphism question
      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. COA bit to fast for mee ;-)
      singulars
      1. PO
      1. USDanielB
    2. COhi, yeah did try that. cannot cast this (BaseFoo<TDerived>) to TDerived though
      singulars
      1. PO
      1. USsambomartin
    3. COSure you can. I just tested it. Maybe you forgot the `where` part?
      singulars
      1. PO
      1. USDaniel Hilgarth
 

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