Hm.
I was able to figure out what it was and do have hack around that.
OracleParam class does certain checks, mainly it chekcs if param is
date/time/timedelta or true/false. Otherwise it converts everything to
string.
And that's where backend thinks that WKTAdapter coming from Oracle GIS
Yes, we have a lot of code in this area. It isn’t particularly complex, but it
isn’t always easy to tell what problem a particular line of code solves either.
I’m afraid “educated guesses” are your best option at this point.
Conditionally skipping some type conversions on sufficiently modern
Unfortunately problem seem to lie somewhere in standard Oracle backend
and it's way to handle arguments and argument types. Most probably it's
FormatStylePlaceholderCursor object that does it.
On 18.05.2016 00:09, Claude Paroz wrote:
Hello Jani,
I'm not familiar with the Oracle backend, but
Hello Jani,
I'm not familiar with the Oracle backend, but you probably have to play
with the
OracleSpatialAdapter / WKTAdapter stuff to achieve what you need. Good luck!
Claude
Le mardi 17 mai 2016 14:53:28 UTC+2, Jani Tiainen a écrit :
>
> I'm toying around Oracle and latest cx_Oracle
I'm toying around Oracle and latest cx_Oracle feature that allows
putting real objects through cx_Oracle to database. One use case is GIS
which is way faster than trying to transfer WKT over queries.
I just have one problem - how I can tell in the backend that one
particular query parameter
