Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Please read: <a href="http://www.codinghorror.com/blog/archives/001281.html" rel="nofollow noreferrer">All Abstractions Are Failed Abstractions</a> It should put a lot of your questions in perspective.</p> <p>Performance is usually not an issue with ORM - and if you really find yourself in a situation where it is, then there usually is always the option to handcraft the SQL statements the ORM uses.</p> <p>IMHO ORM give you an instant and huge development speed increase. That's why they are so popular. And using them right does not make you paint yourself in a corner. There is always the option of hand tuning the performance.</p> <p>Edit:</p> <p>Even though Jeff focuses on Linq to SQL all he says about abstractions and performance are equally true for NHibernate (which I know from years of real world app development). IMHO one should use by default an ORM since they are more than fast enough for the notorious 90% of situations. Reading code written for an ORM usually is more maintainable and readable especially when your code is picked up by the next developer that inherits your code. <a href="http://www.codinghorror.com/blog/archives/001137.html" rel="nofollow noreferrer">Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live.</a> Never forget about that guy! </p> <p>In addition they give out of the box caching, lazy loading, unit of work, ... you name it. And I found that when I was not happy about the performance of the ORM <em>it was MY fault</em>. ORM do force you to adhere to good OO design pratices and help you shape your Domain Model.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat's the current state of ORMs?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTobias Hertkorn
    1. USTobias Hertkorn
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat's the current state of ORMs?
      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. CO+1 since this is my answer (self vote!)
      singulars
      1. PO
      1. USdfa
    2. COI've already read it but Jeff talks mostly about Linq to SQL there, and I'm interested in orms. I know the limitiations of Linq to SQL and find it a convenient tool WHEN you know how to use it and its limitations ... but ... could I say the same about ORMs?
      singulars
      1. PO
      1. USJorge Córdoba
    3. COWhen you say "is usually not an issue with ORM" do you mean they run fast or that you shouldn't use them if you're aiming for performance?.
      singulars
      1. PO
      1. USJorge Córdoba
 

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