Skip to content

feat: Include end token in ALTER TABLE statement #1999

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

Merged
merged 3 commits into from
Aug 9, 2025

Conversation

IndexSeek
Copy link
Contributor

Resolves #1858 in span calculation for ALTER TABLE statements. The span for ALTER TABLE statements was ending too early and not including the semicolon.

@IndexSeek
Copy link
Contributor Author

I'm not sure about the linting violations, I addressed one, but it seemed unrelated to the change.

Copy link
Contributor

@iffyio iffyio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @IndexSeek! Changes look good to me overall, left some minor comments.

The lint failure has been fixed on the latest main so that merging in from main should resolve the failure in this branch

@IndexSeek IndexSeek force-pushed the incorrect-line-ending-spans branch from 3cba41e to 9a42c3f Compare August 9, 2025 01:30
@iffyio iffyio changed the title feat: include end token in ALTER TABLE statement for span calculation feat: Include end token in ALTER TABLE statement Aug 9, 2025
Copy link
Contributor

@iffyio iffyio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks @IndexSeek!
cc @alamb

@iffyio iffyio merged commit 356308b into apache:main Aug 9, 2025
10 checks passed
@agis
Copy link

agis commented Aug 9, 2025

Thanks! I can confirm this solved #1858. Are there any estimates on the next release?

@alamb
Copy link
Contributor

alamb commented Aug 12, 2025

Thanks! I can confirm this solved #1858. Are there any estimates on the next release?

This is the next scheduled release

We mostly do releases on a schedule, but feel free to discss on that ticket if you would like to request an earlier release

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

Successfully merging this pull request may close these issues.

Postgres: Incorrect ending line reported in Span for multi-line query
4 participants