- 3,715,645 Users
- 2,242,819 Discussions
- 7,845,476 Comments
Forum Stats
Discussions
Categories
- 17 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 1.6K Databases
- 466 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 487 MySQL Community Space
- 3 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 416 SQLcl
- 42 SQL Developer Data Modeler
- 184.8K SQL & PL/SQL
- 21K SQL Developer
- 1.9K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 8 DevOps
- 3K QA/Testing
- 247 Java
- 5 Java Learning Subscription
- 10 Database Connectivity
- 66 Java Community Process
- 1 Java 25
- 9 Java APIs
- 141.1K Java Development Tools
- 6 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 10 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 125 LiveLabs
- 30 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 3 Deutsche Oracle Community
- 10 Español
- 1.9K Japanese
- 2 Portuguese
EntityFrameworkCore - querying NCLOB
Hello, I've seen this documentation about annotating a string property with [MaxLength(65536)] to create an NCLOB column:
However, the issue I have is that I cannot query on this property. Comparing to the Devart driver, I can see that that uses a special compare function when it knows the property is mapped to an nclob column. However, with your Oracle driver, even with that annotation, the query does a straight string comparison, which is not allowed and leads to the error "ORA-00932: inconsistent datatypes: expected - got NCLOB"
Is this expected behaviour, or is this a known bug, and is there a way to fix it?
Thanks
Answers
-
Alternative question: how can I raise a bug?
-
This is not a known bug. You can open a service request with Oracle Support with a test case and we'll investigate and provide a fix if it's a problem in the Oracle EF Core code.