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

feat: add Expr::column #852

Merged
merged 1 commit into from
Feb 2, 2025
Merged

feat: add Expr::column #852

merged 1 commit into from
Feb 2, 2025

Conversation

tisonkun
Copy link
Contributor

The same as Expr::value to Expr::val.

I'm using this and now work it around with Expr::col(...).into().

Signed-off-by: tison <wander4096@gmail.com>
Copy link
Member

@ikrivosheev ikrivosheev left a comment

Choose a reason for hiding this comment

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

LGTM

@tisonkun
Copy link
Contributor Author

@ikrivosheev Thanks for your review!

May I ask what the normal process for merging a patch and cutting a new release? I'd expect a new release with this patch so that I can switch my project to depend on the new version for the changeset.

@ikrivosheev
Copy link
Member

@ikrivosheev Thanks for your review!

May I ask what the normal process for merging a patch and cutting a new release? I'd expect a new release with this patch so that I can switch my project to depend on the new version for the changeset.

Well, I'll review a chunk of PR and then merge it and write chabgelog.

After I can prepare a release.

@tyt2y3
Copy link
Member

tyt2y3 commented Feb 2, 2025

Thanks @ikrivosheev ! Let's merge this

@tyt2y3 tyt2y3 merged commit 12639c2 into SeaQL:master Feb 2, 2025
20 checks passed
@tisonkun tisonkun deleted the expr-column branch February 3, 2025 01:29
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.

3 participants