Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I made some research a while ago.</p> <p>One specific question from me, might give you some additional information: <a href="https://stackoverflow.com/questions/454249/would-you-use-nhibernate-for-a-project-with-a-legacy-database-which-is-partly-ou">Would you use NHibernate for a project with a legacy database, which is partly out of your control?</a></p> <p>Some of your points of interest I can answer:</p> <ul> <li>Which is better if you control both the data model and the application?</li> </ul> <p>I can answer it the other way around: If you don't have control over the data model and thus facing some legacy database, iBatis is the better choice.</p> <ul> <li>iBATIS is repeatedly called simpler to learn - does this have long-term maintenance consequences (i.e. easy to start, hard to maintain)?</li> </ul> <p>It depends what you want to do with it. If you have a domain driven development approach then iBatis might get painful by time. If you just do simple data manipulation and don't have a full blown domain model then nHibernate might be a overkill by the time.</p> <ul> <li>Do both make it easy to switch the underlying database vendor?</li> </ul> <p>Both have mechanisms to shield you off from a specific database vendor, but I admit that have not done intense research in this direction.</p> <ul> <li>How skilled do your developers need to be with SQL?</li> </ul> <p>When you use iBatis, you need more SQL skills than NHibernate. Using iBatis you always need to code some SQL. NHibernate doesn't require you to code SQL statements -- it even can do the DDLs for you. Powerful features will require you to go to old good SQL, which will be inevitable.</p> <p>Some other points:</p> <ul> <li><p>I personally find that iBatis much more lightweighter. You can get things done very quickly. NHibernate is more powerful, but has much more features, which you can use in wrong way.</p></li> <li><p>It is possible to combine the use of NHibernate and iBatis! You can use NHibernate for your business logic. For reporting purposes, where you just read data out of tables, fallback to iBatis.</p></li> <li><p>If your application has a longer life cycle and a lot of business logic, consider NHibernate. It has a lot of feature aiding you in handle business objects.</p></li> <li><p>The community around NHibernate is very active and come up with useful tools.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the difference between NHibernate and iBATIS.NET?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USTheo Lenndorff
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat is the difference between NHibernate and iBATIS.NET?
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    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