Note that this idea came from the members of the European user groups at the user group meetings held in March, 2014.
We have had a couple of requests for this from our clients as well as internally from other groups within our company.
Are there certain statements which would be implemented as stored procedures or are all database access statements equally desired? Would a property of the statement indicating that it should be implemented as a stored procedure be sufficient or is there more information needed (such as only implement as a stored procedure for certain database targets or something)?
Mainly our clients are looking to extract information out of our product, so I would think the READ_EACH and READ would be the primary statements. Right now we would have to write these external to the model and for each database platform we support. Another option that has also been requested it to create and use database Views. I don't know if Gen supports that or not. It seems like the same basic idea. I think the Gen requires everything to be a physical table.
cbeazley.1 Could you open up another idea for support for Database views? I agree that it would be a pretty basic idea and would reuse a lot of what is already in the product. I've actually modeled views before but just haven't included them in the generated DDL and been real careful not to do anything but READ them (although it seems like I remember that some databases support updates on views as well). Thanx!
We're looking into how we might want to implement stored procedures. Doing it at the statement level is certainly one choice.
In Finnish User Group we were interested in publishing action diagram logic as a stored procedure, not single sql-statements.
Retrieving data ...