Realise it is on the roadmap but executing stored procedures would really make this a useful library.... about querybuilder HOT 10 CLOSED

How is it on the backlog when this case is closed? :-)

from querybuilder.

Hi, do you have any suggestion on what needed exactly ?

from querybuilder.

Hi @ahmad-moussawi,

• Support for both SP's that don't return results, do return results, return multiple datasets as part of their results
• Ability to easily compose a stored proc call which mainly comprises adding parameters and values so something like:

var fastCarsStoredProc = new StoredProc("usp_FastCars")
    .Param("Param1", 120)
    .Param("Param2", 120, dirOut)   //Enum for directionality of params

Perhaps taking some insights from https://github.com/StackExchange/Dapper#stored-procedures

from querybuilder.

Now you can execute stored procedure using the QueryFactory.Statement method

db.Statement("exec procname ?", new object[] {"param1"});

from querybuilder.

@ahmad-moussawi Ummmm that will work, but is basic string replace ;-). So you are planning to add proper support for Stored Procs?

from querybuilder.

@natiki, sorry my experience with Stored Procedure is limited, can you lists the features that you want to be added ? if yes do you a PR for them ?

from querybuilder.

@ahmad-moussawi see #52 (comment) and my suggestion to use the Dapper approach for the API.

from querybuilder.

@ahmad-moussawi This really needs to be added back as a feature..... Being able to execute stored procedures, functions is a must have to make this library useful ;-)

from querybuilder.

@natiki, thanks for your feedback, but currently it's not on the priority list, I will keep it in the BackLog for now

from querybuilder.

Listed in the docs now.

from querybuilder.