Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] Intro page for indexes and constraints in explore section #11607

Closed
rkarthik007 opened this issue Feb 28, 2022 · 0 comments · Fixed by #18439
Closed

[Docs] Intro page for indexes and constraints in explore section #11607

rkarthik007 opened this issue Feb 28, 2022 · 0 comments · Fixed by #18439
Assignees
Labels
area/documentation Documentation needed temp/docs-migration TEMPORARY USE for migrating docs tickets to Jira

Comments

@rkarthik007
Copy link
Collaborator

Description

We need some introduction on the landing page itself, just like we do for Transactions. This should cover the following:

  • A high level paragraph talking about the following:
    • How the reuse of PG means we support a lot of indexes and their semantics
    • How indexes use distributed transactions internally.
    • We should eventually link out to a docs page in the develop section once its ready
  • Have a table about which index types are supported in YSQL and YCQL - use this table to add links to the various sections.
  • Talk about differences from PG: BTREE indexes, etc
  • Talk about what PostgreSQL indexes are not supported, and link to the page that shows what PG functionality is not supported. Example: GIST, etc (with a link to the github issues)
@rkarthik007 rkarthik007 added the area/documentation Documentation needed label Feb 28, 2022
@polarweasel polarweasel added the temp/docs-migration TEMPORARY USE for migrating docs tickets to Jira label Feb 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Documentation needed temp/docs-migration TEMPORARY USE for migrating docs tickets to Jira
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants