Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think there are a few things you can do that together could help with your design. I also think that you might want to read up on <a href="http://en.wikipedia.org/wiki/Dependency_injection" rel="nofollow noreferrer">Dependency Injection</a> as perhaps providing a better design pattern for what you want to do.</p> <p>Assuming you just want to make what you have work though:</p> <ul> <li><p>First, remove the <code>static</code> methods from your <code>User</code> class, since they 'create' users, and therefore are best just left on the <code>UserMapper</code>.</p></li> <li><p>After that, there will still be a number of methods potentially that use <code>UserMapper</code> functionality from the <code>User</code> class. Create an interface <code>IUserLookup</code> (or something) that supports the <code>UserNameExists</code> and <code>UserNamePasswordExists</code> methods; put this interface in the same project as the <code>User</code> class.</p></li> <li><p>Implement the <code>IUserLookup</code> on the <code>UserMapper</code> class, and then 'inject' it into the <code>User</code> class instances it creates with the static methods through a constructor, so basically, as the <code>UserMapper</code> creates <code>User</code> objects, it gives them a reference to the <code>IUserLookup</code> interface that it implements itself.</p></li> </ul> <p>In this way, <code>User</code> only uses methods on <code>IUserLookup</code>, which is in the same solution, so no reference needed. And <code>UserMapper</code> references this solution, so it can create <code>User</code> objects and implement the <code>IUserLookup</code> interface.</p>
    singulars
    1. This table or related slice is empty.
    1. POCircular reference between Assemblies in C# and Visual Studio 2005
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USjerryjvl
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCircular reference between Assemblies in C# and Visual Studio 2005
      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. COAfter implementing the idea of "Interface-Implementation" in c# and VS2005 I actually found that, implementing interfaces is solving the problem but not fulfilling my target. My target is to work only with BO-layer/assembly from the UI layer/Assembly. So that I can maintain a clean layer-to-layer reference. Coz I don't want a reference to be added both for BO-layer/assembly and ORMapper-layer/assembly in the UI-layer/assembly. I only want to work with BO-layer/assembly from within UI-layer/assembly. Meanwhile someone suggested me that, it can only be possible with using Reflection, not DI.
      singulars
      1. PO
      1. This table or related slice is empty.
    2. COIn essence you are then making your ORM layer de-facto part of the BO layer. The idea or ORM/BO is that you make the BO layer responsible for the functionality that the business objects embody, but the ORM layer is responsible for materialising and storing the objects. Hiding ORM behind BO is going to break the separation of concerns the ORM/BO split is supposed to be for.
      singulars
      1. PO
      1. USjerryjvl
 

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