Mark Ford

PostgreSQL incorrect data on numerics as stCurrency

Ignore this! Apparently Oracle 19 cloud just automatically changed my clob to securefle even though it was create with basicfile. I'm not sure what's that about, but will test further.

x64 lcmOnLoad with later oci.dlls fail to load CLOBs

I just did some testing with x64, clobs and basicfile vs securefile and didn't see any issues. lcmOnLoad seemed to work just fine? If you create a new table with a test clob does it work?

I can verify this issue when using 64bit, Oracle, and the "codepage=UTF16" setting. I see VARCHAR2(4000) fields coming back empty and the ORA-01406 error at fairly random times. Interestingly enough varchar fields smaller than 255 always seem to work for me. I don't see any memory overrun or corruption reports from my debugmode testing so far.

I can verify this issue when using 64bit, Oracle, and the "codepage=UTF16" setting. I see VARCHAR2(4000) fields coming back empty and the ORA-01406 error at fairly random times. Interestingly enough varchar fields smaller than 255 always seem to work for me. I don't see any memory overrun or corruption reports from my debugmode testing so far. I don't use UTF16 in Zeoslib in general so I'm not sure what the use case is for it.

I agree! I was probably trying to be overly careful in preserving the old behavior. Thanks!

Firebird table column comments not shown.