8000 Feedback: Read Committed Transactions - standard terminology: check constraint · Issue #19697 · cockroachdb/docs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Feedback: Read Committed Transactions - standard terminology: check constraint #19697
Open
@hand-crdb

Description

@hand-crdb

Page: https://cockroachlabs.com/docs/v25.2/read-committed.html

What is the reason for your feedback?

[ ] Missing the information I need

[ ] Too complicated

[ ] Out of date

[ ] Something is broken

[X] Other

Additional details

The page uses nonstandard / unclear / non-specific terminology when it uses the word "check" when it should use the phrase "check constraint".

The page currently says

Multi-column-family checks during updates are not supported under READ COMMITTED isolation. #112488

The page should say (my emph. italics)

Multi-column-family check constraints during updates are not supported under READ COMMITTED isolation. #112488

A "check" could mean many things in the database world, while "check constraint" has a well-known specific meaning that is precisely what is being discussed here.

THANK YOU

Jira issue: DOC-13866

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0