Hi everyone.
We have discovered a problem when using a query that contains a cursor expression in our source_type_collection_feed GET handler. We’re using cursor expressions to build hierarchy into our JSON dataset because ORDS converts nested cursors into JSON arrays (thanks for that).
With this type of query and the p_source_type of source_type_collection_feed (for multiple rows) we get a 500 response with the detailed ORDS error:
declares the following explicit parameters, but does not reference them: page_size
We have no idea what the parameter page_size is. If we just change the p_source_type to source_type_collection_item then all is well, a 200 response and the nested cursor converted into a JSON array. Of course, this only returns one row from our dataset so it’s not suitable for us but it does prove that nested cursors are valid in ORDS.
My question, is this a known issue or by design?
Many thanks for ORDS.