Skip to content

Failure while parsing GIN Index #1706

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

Open
LucaCappelletti94 opened this issue Feb 5, 2025 · 1 comment
Open

Failure while parsing GIN Index #1706

LucaCappelletti94 opened this issue Feb 5, 2025 · 1 comment

Comments

@LucaCappelletti94
Copy link
Contributor

The parsing of the CREATE INDEX case, is currently incomplete. Here follows a couple of examples:

CREATE INDEX users_name_trgm_idx ON users USING gin (concat_users_name(first_name, last_name) gin_trgm_ops);

which raises:

CREATE INDEX projects_name_description_trgm_idx ON projects USING gin (concat_projects_name_description(name, description) gin_trgm_ops);: ParserError("Expected: ), found: gin_trgm_ops")

Or analogously:

CREATE INDEX sample_containers_barcode_trgm_idx ON sample_containers USING gin (barcode gin_trgm_ops);

which raises:

CREATE INDEX sample_containers_barcode_trgm_idx ON sample_containers USING gin (barcode gin_trgm_ops);: ParserError("Expected: ), found: gin_trgm_ops")

I will be attempting shortly to do a PR adding support for these use cases.

@LucaCappelletti94
Copy link
Contributor Author

Right now, an Index only supports columns as defined by a OrderByExpr, which I do not believe is general enough to also handle the aforementioned cases. Is this correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant