Databases
StackOverflow2013
Postsdbo
PODatabase independence
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODatabase independence
    primarykey
    data
    text
    <p>We are in the early stages of design of a big business application that will have multiple modules. One of the requirements is that the application should be database independent, it should support SQL Server, Oracle, MySQL and DB2.</p> <p>From what I have read on the web, database independence is a very bad idea: it would result in a hard-to-maintain code, database design with the least-common features in all supported DBMSs, bad performance and bad scalability. My personal gut feeling is that the complexity of this feature, more than any other feature, could increase the development cost and time exponentially. The code will be dreadful. </p> <p>But I cannot persuade anybody to ignore this feature. The problem is that most data on this issue are empirical data, lacking numbers to support the case. If anyone can share any numbers-supported data on the issue I would appreciate it.</p> <p>One of the possible design options is to use Entity framework for the database tier with provider for each DBMS. My personal feeling is that writing SQL statements manually without any ORM would be a "must" since you have no control on the SQL generated by the entity framework, and a database-independent scenario will need some SQL tweaking based on the DBMS the code is targeting, and I think that third-party entity framework providers will have a significant amount of bugs that only appear in the complex scenarios that the application will have. I would like to hear from anyone who has had an experience with using entity framework for database-independent scenario before. </p> <p>Also, one of the possibilities discussed by the team is to support one DBMS (SQL Server, for example) in the first iteration and then add support for other DBMSs in successive iterations. I think that since we will need a database design with the least common features, this development strategy is bad, since we need to know all the features of all databases before we start writing code for the first DBMS. I need to hear from you about this possibility, too.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChristian Conti-Vock
    1. USMuhammad Adel
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODatabase independence
      1. USgbn
      1. VTFavorite
    2. VO
      singulars
      1. PODatabase independence
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODatabase independence
      1. USTsar
      1. VTFavorite
    1. CO"writing sql statements manually without any ORM would be a must since ... a database independent scenario will need some sql tweaking." Au contraire, that is exactly what the ORM will do for you, unless your queries are way complicated. A good ORM will generate appropriate SQL for whichever database it happens to be targeting, no tweaking required. And if you do have way complicated queries, why not just test a few of them with the required EF providers? Give them a try-out rather than just going "well, they're bound to have bugs, oh well, back to handcrafting SQL"!
      singulars
      1. PODatabase independence
      1. USitowlson
 

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