Home/ Questions/Q 8821363
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T05:50:07+00:00

I’m currently building a query builder in C#, which first starts by prompting the

  • 0

I’m currently building a query builder in C#, which first starts by prompting the user to specify which database they would like to query on their local machine.

Thus, the program allows databases to be “plugged-in” to it, rather than have a number of databases with tables that are always used.

Thus, for my query builder to generate SQL statements, would it make more sense to output and execute SQL statements in the form of strings, or could I use Entity Framework? I have no experience with Entity Framework, however from what I can understand, it makes more sense to utilise EF if you’ve got a static database whose tables and schema you are aware of – versus potentially any database being specified by the user at run-time.

I’ve currently been working with SQL statements – i.e. the users’ interaction with the query builder, literally executes string-based SQL statements which are generated by the application. Would it be possible or worthwhile to switch to Entity Framework?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From my experience using EF, if you are generating queries dynamically, you’re better stick to SQL strings.

    The only way you could use EF to query a unknown schema is by generating the Entities through reflection, which would be a hell of lot of work. And I’m not sure it would work. And also, you’d lose all benefits from using EF.

    So, if this is the case, no.

    • 0