Sign in to follow this  
Toolmaker

Designing a Data Access Layer

Recommended Posts

This is a little question discussing the software engineering aspect of building a DAL. Hints on techniques(such as datasets / linq) aren't required. I'm currently developing a small application to rank debating tournaments. It uses an MS SQL Server 3.5 CE and I'm using Datasets for accessing the databases. However, I'm currently in doubt on what to do with reading/writing to the database. I need a connection string to connect to the database, and I have various business logic classes that need to be stored in the database. Should I just go with a complete Database class that stores the connection string and handles all the database work, or is there a nice and robust way to model a database access layer around this? Toolmaker

Share this post


Link to post
Share on other sites
There are numerous frameworks that will handle this for you, depending on what language you are using. Here's a short list. Hibernate is the only one I have experience with, though. It mostly works through establishing an XML mapping between objects and tables.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this