It looking at the possibility of using sql2java to generate code wrappers around stored procedure calls. JDBC has some API methods like supportsStoredProcedures(), getProcedures(), getProcedureColumns() and getProcedureTerm() which could be used to retrieve the database stored procedures, including parameters information. This could be added to the method load() of the class Database.
Do you consider this to be worth the effort ?? How much do you think it could take me to understand all the code and the template file structure ??
Besides, if I change the default SQL generation for CRUD into procedure calls, how should I differentiate CRUD SPs from the others ?? Should I rest on naming conventions and pattern filtering ?? (I'm assuming getProcedures() supports patterns filtering, just the same as getTables).
Thanks for your input !!
Daniel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all !!
It looking at the possibility of using sql2java to generate code wrappers around stored procedure calls. JDBC has some API methods like supportsStoredProcedures(), getProcedures(), getProcedureColumns() and getProcedureTerm() which could be used to retrieve the database stored procedures, including parameters information. This could be added to the method load() of the class Database.
Do you consider this to be worth the effort ?? How much do you think it could take me to understand all the code and the template file structure ??
Besides, if I change the default SQL generation for CRUD into procedure calls, how should I differentiate CRUD SPs from the others ?? Should I rest on naming conventions and pattern filtering ?? (I'm assuming getProcedures() supports patterns filtering, just the same as getTables).
Thanks for your input !!
Daniel