more data type information about object types about odpi HOT 6 CLOSED

I'll take a look and will implement this suggestion if there aren't any difficulties in doing so!

from odpi.

Thank you! I'm looking forward to it.

from odpi.

I created the structure dpiDataTypeInfo as suggested. Thanks! It made sense. The nullOk member is only relevant for queries (not object attributes and collection elements) but the other members all do make sense, and it simplified the code a fair bit, too. Take a look and let me know if that answers your request.

from odpi.

Thank you!

When I wrote the dpiDataTypeInfo, I didn't realize that nullOK is unavailable for object attributes and collection elements. Sorry to bother you, but could you remove the nullOk member from the dpiDataTypeInfo and put it back to dpiQueryInfo? I think that it is better. Well, if my request looks inappropriate, feel free to reject it.

I found a related potential bug.
In dpiStmt__getQueryInfoFromParam, DPI_OCI_HTYPE_DESCRIBE is used as the handle type of the param value. Though it works, it should be DPI_OCI_DTYPE_PARAM because the param is got from OCIParamGet.

from odpi.

When I wrote the dpiDataTypeInfo, I didn't realize that nullOK is unavailable for object attributes and collection elements. Sorry to bother you, but could you remove the nullOk member from the dpiDataTypeInfo and put it back to dpiQueryInfo? I think that it is better.

Agreed. I looked at the documentation and it is explicitly forbidden on object attributes and collection elements -- so I have moved it back as suggested. Thanks.

I found a related potential bug. In dpiStmt__getQueryInfoFromParam, DPI_OCI_HTYPE_DESCRIBE is used as the handle type of the param value. Though it works, it should be DPI_OCI_DTYPE_PARAM because the param is got from OCIParamGet.

It does indeed work so I'll ask about what the correct code ought to be when I ask about the precision attributes, too. Thanks for your feedback.

from odpi.

Thank you!
What I want was added.

from odpi.