in theory that makes sense but dumping out the values passed into bind
doesn't show any out of the ordinary characters. when we substitute the
binds for literals with literal_binds, those literals all look like
standard ascii values.
i just got an email from the developer that the problem has disappeared
after upgrading to latest version of SQLAlchemy and project specific code
On Thu, Oct 3, 2019 at 3:27 PM Norman Dunbar <oracle@xxxxxxxxxxxxxxx> wrote:
Your columns and binds are looking like they use different and
incompatible charactersets. Some charactersets cannot be compared -
resulting in what you are seeing here. When you changed from varchar2 to
nvarchar2 you were using the same characterset in the two sides of the
In a eord, or two, you are now comparing apples, before it was apples and
oranges. You see this in the csid values in the two ora-12704 lines in your
I might be wrong but usually, binds appear before the exec in the trace.
From the look of things your sql is parsed then the error is detected, but
it doesn't appear as a parse error line, then the cursor is closed - hard
closed - so no exec and that's possiblt why the binds are missing.
Most of the ora-12704 lines are the same as the binds would be, the just
have different names.
Sent from my Android device with K-9 Mail. Please excuse my brevity.