- 382.3K All Categories
- 2.1K Data
- 209 Big Data Appliance
- 1.9K Data Science
- 448K Databases
- 221K General Database Discussions
- 25 Multilingual Engine
- 520 MySQL Community Space
- 467 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 492 SQLcl
- 3.9K SQL Developer Data Modeler
- 186.2K SQL & PL/SQL
- 21K SQL Developer
- 293.3K Development
- 7 Developer Projects
- 128 Programming Languages
- 290K Development Tools
- 95 DevOps
- 3K QA/Testing
- 645.5K Java
- 24 Java Learning Subscription
- 36.9K Database Connectivity
- 149 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.9K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 16 Java Essentials
- 144 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 198 Java User Groups
- 266 LiveLabs
- 36 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 166 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 230 Portuguese
OraOLEDB is still crazy
If there is no way to reply to archived discussions,
they don't seem to know that they tend to waste much time more than 120 days to solve the problems of their products.
(The reason why they archive discussions might be because they might know that the problems would be never solved.)
> In THIS APRIL(after March, 2015), we built the LATEST(*) 18.104.22.168 client environment.
> As a result, we found new behavior of OraOLEDB...
In the end of THIS SEPTEMBER, we build LATEST(*) 22.214.171.124 client environment.
*)You should ask Oracle Support how to update 126.96.36.199 client to latest revision.
As a result, we found new behavior of OraOLEDB...
---- our result ----
They seem to stop appending crazy blanks at last.
The value "202" of "Type" means "adVarWChar".
The number of characters of the value of CHAR(4 BYTE) is "less than or equal to" 4(VARIABLE-characters)
even though the number of bytes of the value is "just equal to" 4(FIXED-bytes)
when the encoding is JA16SJISTILDE(VARIABLE-width 2 byte character set).
Had they recovered their senses?
Why do they still believe that DefinedSize of "EQ" must be "2"?
Why do they cause inconsistencies to cause inconsistencies?