New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQL : Stored procedure support #15
Comments
Closing this for now, since I couldn't find a way to provide typesafe stored procedure support in Querydsl. Feel free to reopen this. |
The PreparedStatement.getParameterMetaData() on the SP can be queried in JDBC to generate the types isn't it? |
But is this available via database metadata? |
Should this not work the same way as tables for the parameter and proc name? For the returned resultset of the prodedure, we can pass in a bean class as On Fri, Jan 25, 2013 at 2:13 PM, Timo Westkämper
|
One of the tricky situations may be to properly handle things like the in-out parameters and get them registered in the call, but all this info comes in the metadata so the generated code should be able to handle it easily. |
Would be very nice to see this features - and it's a feature JOOQ has: http://www.jooq.org/doc/3.2/manual/sql-execution/stored-procedures/ |
I just used stored procedure support for JPA 2.1 and it did a good work. https://docs.oracle.com/javaee/7/api/javax/persistence/NamedStoredProcedureQuery.html |
Add CodeWriter.getClassConstant() to abstract the difference between A.class in Java and classOf[A] in Scala.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Stored procedure support
Pseudocode
The text was updated successfully, but these errors were encountered: