n1ql error parsing should use error codes for indexes

Description

We currently do string parsing in gocb, this should really be in gocbcore and using codes.

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Activity

Show:

Charles Dixon November 28, 2023 at 5:00 PM

When we do this we should also add handling for any error codes that we don't handle but other SDKs do. This means it'll need to go into a minor release as some of the semantics might technically change.

Charles Dixon November 28, 2023 at 4:41 PM

We do actually use codes in gocb, but all this logic should live in gocbcore.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Sprint

Fix versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created October 4, 2023 at 4:25 PM
Updated December 12, 2023 at 4:00 PM
Resolved December 12, 2023 at 4:00 PM
Instabug