Jump to content
  • Advertisement
Sign in to follow this  
Toolmaker

Designing a Data Access Layer

This topic is 3599 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

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
Advertisement
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
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!