Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your code does implement the pattern but not to the full extent which C# allows, in other words - you are not using the important benefits of the C# language.</p> <p>Here is an example of how you can do it better:</p> <pre><code> class Program { static void Main(string[] args) { var myEngineer = ProfessionFactory.CreateProffession&lt;Engineer&gt;(); var myDoctor = ProfessionFactory.CreateProffession&lt;Doctor&gt;(); myEngineer.EnginerringStuff(); myDoctor.HealingPeople(); var myEngineer2 = (Engineer)ProfessionFactory.CreateProffession("Engineer"); //using the other method I still have to cast in order to access Engineer methods. //therefore knowing what type to create is essential unless we don't care about engineer specific methods, //in that case we can do: var myEngineer3 = ProfessionFactory.CreateProffession("Engineer"); //which is useless unless we start involving reflections which will have its own price.. } public interface IProfessionFactory { IProfession CreateObj(); } public interface IProfession : IProfessionFactory { string ProfessionName { get; } } public abstract class ProfessionFactory : IProfessionFactory { public abstract IProfession CreateObj(); public static T CreateProffession&lt;T&gt;() where T:IProfessionFactory, new() { return (T)new T().CreateObj(); } public static IProfession CreateProffession(object dataObj) { if (dataObj == "Engineer") return CreateProffession&lt;Engineer&gt;(); if (dataObj == "Doctor") return CreateProffession&lt;Doctor&gt;(); throw new Exception("Not Implemented!"); } } public class Engineer : IProfession { public string ProfessionName { get { return "Engineer"; } } public IProfession CreateObj() { return new Engineer(); } public void EnginerringStuff() {} } public class Doctor : IProfession { public string ProfessionName { get { return "Doctor"; } } public IProfession CreateObj() { return new Doctor(); } public void HealingPeople() {} } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POFactory pattern with 4 layer architecture
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USG.Y
    1. USG.Y
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is just at a glance, but having a Doctor inherit from a ProfessionFactory doesn't sound right.
      singulars
      1. PO
      1. USMathias
    2. CODoctor is both a profession and a little factory to create doctors. Acutally I'll revise as any profession is also a profession factory.
      singulars
      1. PO
      1. USG.Y
    3. COIMO, the statement "this class is two things" (a profession, and a factory) is a bit of a smell, and tends to indicate that it doesn't follow the single responsibility principle.
      singulars
      1. PO
      1. USMathias
 

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