Details
-
Job Story
-
Resolution: Fixed
-
Critical
-
2.0.2
-
None
-
Security Level: Public
-
None
Description
This issue tracks the various issues relative to support of the N1QL query engine as of developer preview 4 (dp4).
Attachments
Issue Links
- depends on
-
JVMCBC-124 fix IndexOutOfBounds when processing query results
- Resolved
-
JCBC-665 support N1QL dp4 statements with parameters
- Resolved
-
JCBC-674 Offer an API/DSL for prepared statements
- Resolved
-
JCBC-678 Expose all possibilities of query parameters in a Parameter Object
- Resolved
-
JCBC-685 DSL for escaping identifiers
- Resolved
-
JVMCBC-94 Allow GenericQueryRequest to take a json query
- Resolved
-
JVMCBC-105 correctly parse dp4 responses
- Resolved
-
JVMCBC-117 Implement PreparedStatementQueryRequest
- Resolved
-
JCBC-676 Offer factory methods on Query
- Resolved
-
JCBC-677 remove Bucket.queryRow and AsyncBucket.queryRaw from the visible API
- Resolved
-
JCBC-680 Adapt (Async)QueryResult to the new response data
- Resolved
-
JCBC-683 allow querying with raw statements
- Resolved
-
JCBC-687 Make QueryResult block until all data is available
- Resolved
- has to be done before
-
JVMCBC-118 Improve resource management in Query responses
- Resolved
- relates to
-
JCBC-759 Document N1QL Querying and Behaviour
- Resolved