rlangham wrote:
I am using the demo version and curious about a few things...
1) Does it have an option to create the insert/update/insert SQL statements for a table, and then we can import these into the database and have the generated .NET code call the stored procedures. We have security requirements where all statements of this type must be in stored procedures, not SQL statements on the client side?
We don't support procs for CUD operations during entity operations, as in: save an object graph and while saving call procs instead of generate code.
You could of course modify the sourcecode for the DQE (SQL engine) for the DB you're using (every customer can access/modify the runtime lib sourcecode) and emit calls to procs, obtained from a list) instead of generating SQL though this isn't recommended.
2) In the example generated code for my table, I saw Update and Delete routines, but did not see an Add routine. There appears to be an AddEntity low-level method, but did not generated code using this routine
Selfservicing? In which class were these routines located? Please provide more information.
3) Appears to be DataReader support in the low-level code, but no generated code that returns this, only DataSet. Any option for this?
You can fetch any query as a datareader, and also project the datareader onto any other class. Please check in the documentation: using the generated code -> selfservicing/adapter -> Fetching DataReaders and projections.
It contains an example with a stored proc as well.
