Skip to content

Prepare for 0.55.0 release: Version and CHANGELOG #1750

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 9 commits into from
Feb 27, 2025

Conversation

alamb
Copy link
Contributor

@alamb alamb commented Feb 26, 2025


This release consists of 56 commits from 25 contributors. See credits at the end of this changelog for more information.

**Breaking changes:**
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I also figured I would highlight some particularly significant changes

Copy link
Contributor

Choose a reason for hiding this comment

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

I would suggest also mentioning the changes from #1739 here because it changes the names of several DataType variants and could be pretty disruptive.

@alamb alamb marked this pull request as ready for review February 26, 2025 21:49
@alamb
Copy link
Contributor Author

alamb commented Feb 26, 2025

FYI @iffyio

@alamb alamb mentioned this pull request Feb 26, 2025
5 tasks
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!

@lovasoa
Copy link
Contributor

lovasoa commented Feb 27, 2025

Can we add a small migration guide to minimize the impact of the Expr::Value change ? I suggest:

Migrating usages of Expr::Value

Since v0.55, sqlparser the Expr::Value enum variant contains a ValueWithSpan instead of a Value. Here is how to migrate.

When pattern matching

- Expr::Value(Value::SingleQuotedString(my_string)) => { ... }
+ Expr::Value(ValueWithSpan{ value: Value::SingleQuotedString(my_string), span: _ }) => { ... }

When creating an Expr

Use the new Expr::value method (notice the lowercase v), which will create a ValueWithSpan containing an empty span :

- Expr::Value(Value::SingleQuotedString(my_string))
+ Expr::value(Value::SingleQuotedString(my_string))

@alamb
Copy link
Contributor Author

alamb commented Feb 27, 2025

Can we add a small migration guide to minimize the impact of the Expr::Value change ? I suggest:

Thank you -- added in db7911b

@alamb
Copy link
Contributor Author

alamb commented Feb 27, 2025

Inpired by @lovasoa I also pushed a commit with a note about ObjectName

Migrating usages of ObjectName

In v0.55 of sqlparser, the ObjectName structure has been changed as shown below. Here is now to migrate.

- pub struct ObjectName(pub Vec<Ident>);
+ pub struct ObjectName(pub Vec<ObjectNamePart>)

When constructing ObjectName

Use the From impl:

- name: ObjectName(vec![Ident::new("f")]),
+ name: ObjectName::from(vec![Ident::new("f")]),

Accessing Spans

Use the span() function

- name.span
+ name.span()

@alamb
Copy link
Contributor Author

alamb commented Feb 27, 2025

Pushing this and will now make the release

@alamb alamb merged commit ed41654 into apache:main Feb 27, 2025
9 checks passed
@alamb alamb changed the title Prepare for 55.0.0 release: Version and CHANGELOG Prepare for 0.55.0 release: Version and CHANGELOG Feb 27, 2025
ayman-sigma pushed a commit to sigmacomputing/sqlparser-rs that referenced this pull request Apr 10, 2025
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.

4 participants