Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It sounds like you have a number of (I would guess relatively small) apps to rewrite, so I'd be tempted not to use an ORM right off the bat. For your first app, just try writing the data access code yourself using ADO - but try and make sure everything is well-separated, for example by using the <a href="http://martinfowler.com/eaaCatalog/repository.html" rel="nofollow noreferrer">Repository</a> pattern. This way, if you decide to, you could swap out your ADO DAL for something using an ORM fairly easily.</p> <p>Once you've done it yourself, you'll have a better understanding of what an ORM can do for you and whether you want to use one or not (which you probably will!).</p> <p>Also, and this really depends what type of app you're writing, but I'd suggest sorting the Model out first (the core classes of your app, commonly 'Employee', 'Order' and so on), and then make your data access based on that. Doing it this way, you could use something like EF4, NHibernate and so on, which can generate the database schema based on your .Net model classes. (Although it would mean you can't use Linq to SQL as easily, as that requires having the database in place first).</p> <p>If you did want to use an ORM, and you're using SQL Server, <a href="http://msdn.microsoft.com/en-us/library/bb386976.aspx" rel="nofollow noreferrer">Linq to SQL</a> is easy to get going with. The main downsides are you can't do model-first development, it only supports SQL Server, and it's no longer in active development so might no be a good thing to spend learning time on.</p>
    singulars
    1. This table or related slice is empty.
    1. POShould a .Net beginner bother with ORM or wait until he gets more experience?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USGrant Crofton
    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. 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