Typical Issues
- Symptom: Users encounter the following exception when calling a stored procedure, even though they have bound input parameters of a user-defined type and registered output parameters for the procedure:
ERROR: Function public.test_proc(compfoo, public.compfoo_table, compfoo, public.compfoo_table) does not exist. ???No function matches the given name and argument types. You might need to add explicit type casts.
Cause: The user-defined type bound to the input and output parameters does not match the one set in the stored procedure.
Solution: Keep the user-defined type bound to the input and output parameters consistent with the one set in the stored procedure.
- Symptom: Users encounter the following exception when calling a stored procedure, even though they have bound input parameters of a user-defined type and registered output parameters for the procedure:
java.lang.RuntimeException: org.postgresql.util.PSQLException: ?? CallableStatement ????????????? java.sql.Types=1111 ?? 1?????????? java.sql.Types=2002?
Cause: The enableGaussArrayAndStruct parameter is set to true when pgArray compatibility is in effect. However, it is impossible to maintain compatibility with both pgArray and GaussArray simultaneously.
Solution: When pgArray compatibility is in effect, check for and delete enableGaussArrayAndStruct=true.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot