MS SQL supports \"Inline Table-valued Functions\".
These can be treated like a View, but defined with parameters. You can think of them as a cross between a Stored Procedure and a View.
As such, MyGeneration should list them with all the \"output\" columns, and with all the \"input\" parameters.
Currently, they are listed in the \"Procedures\" listing, but without the output columns. These columns are predefined and immutable, like a View.
Also, these table functions cannot be called like a normal stored procedure. Templates would need to handle them differently. However, the MyMeta browser does not show any properties to distinguish between them. From the browser, I can't tell whether the \"procedure\" is a \"stored procedure\" or a \"table in-line function\".
So, two issues:
- columns are not known for table functions
- table functions are mixed in with stored procedures and not identifiable