Database access

I want to write a new application that will use the DBMS. During the development stages of this application and weighing the options, I learned that there will be a lot of database access, which means a lot of queries. My biggest problem while designing this system is the cumbersome nature of SQL queries, updates and deletes scattered throughout the code. Are there language syntax extensions (or scripting languages) behind Linq (which I don't like because of the awkward syntax) that are available today? I am very familiar with Progress ABL (their 4GL independently) for development and I like the syntax it has, but its deployment model and dependencies for my type of application are heavy and costly.

The system requested must be PHP or C # compatible.

The database management systems that I plan to use are SQLite, MySQL or MSSQL (Compact or Standard).

0


source to share


4 answers


just don't scatter SQL in your code. write the correct model layer.



even if you don't use an MVC or ORM framework, using proven development approaches are always paid. just write a list of conceptual objects stored in your database with all the operations you want to perform on them and write all the functions to do this in one file (or a file for each concept object). the rest of the program should not have a single SQL command, everything should be done using this model layer.

+1


source


You might want to consider an ORM like nHibernate that will work with or without LINQ.



+2


source


If you are using C # you can use something like Subsonic to access the database. It will handle your data access, and in many cases, you will be able to avoid writing SQL in all of your code.

0


source


Any database interface will prevent you from having SQL in your code, but there still has to be data access in some way, and usually you end up with proprietary junk that you were frustrated with. I used to use Hibernate, this is a great and powerful java library that tells you about your database. If your tasks are small, then cheese access is not a very bad idea, as the sql in your code is bad if the database ever changes, although it probably will.

0


source







All Articles