Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Agreed with @Aiden Bell. But I think you are right in pointing out the differences. I use LINQ to SQL which in your definition is simply Active-Record style of ORM. For me this works great as I work on a lot of greenfield apps and start at the db to build out my classes. From there I tend to follow a Domain Driven Design approach (I know...this is a classes first concept) working with my generated classes. To me this gets me down the road quickly.</p> <p>Having said this I have also worked with Entity Framework and NHybernate. Entity Framework is the UBER data mapper and NHybernate is also a data mapper but without as much complexity! I personally feel that Entity Framework has a long ways to go. If I was ever to need more complexity such as in a brownfield application where the db was fairly set in stone and I needed to get my classes to represent my application rather than my database then I would prefer to move to something more along the lines of NHybernate and its data mapping funcationality.</p> <p>I think each of these tools has it's place. It is not fair to say that they are all the same as they are not. An active record is great in that it generates classes for me that directly represent my database. This works when I created the database or the database closely represents my ubiquitous terms and concepts of the application. The mapping types of orms work when I have a fixed db that doesn't make sense or clearly map to my application in which case I can encapsulate the complexity or lack there of in my database to create a rich domain via the mapping features of the ORM tool.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the difference between a ORM, AR, QB, & DM?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAndrew Siemer
    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. This table or related slice is empty.
    1. This table or related slice is empty.
 

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