Open markddrake opened 4 years ago
This is a known limitation. Its on the list of things we intend to correct at some point but I'll let @cjbj comment on priorities!
This is related to ODPI-C issue 25.
Guys, its a really huge issue for us. We had to implements non normal type hierarchy but ... like:
BASETYPE |----> SUBTYPE1 |----> SUBTYPE2
CONTAINER_TYPE ( SUBTYPE1FIELD SUBTYPE1, SUBTYPE2FIELD SUBTYPE2 ) *** and set only one of SUBTYPE1FIELD or SUBTYPE2FIELD.
instead of CONTAINER_TYPE ( BASETYPEFIELD BASETYPE )
Its like a hack :(
Noted.
See https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html for how to report security issues.
With the async/await programming style, make sure you are using 'await' in the right places.
Is it an error or a hang or a crash?
error
What error(s) you are seeing? Incorrect conversion of PL/SQL types to JSON
Include a runnable Node.js script that shows the problem. Include all SQL needed to create the database schema. Use Markdown syntax, see https://help.github.com/github/writing-on-github/basic-writing-and-formatting-syntax
Run the following sql script to creates required types, table and rows..
This should create a table with the following rows
Now run the following node program
The output is
As you can see it has only output the attributes defined by the base type, it has not output the attributes defined by the sub-types. I would have expected it to output all the information. Another issue is should it also output the 'type' itself, so the program processing the data does not have to try to guess which type or subtype the data is an instance of.