Skip to content

Add User to README #787

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 1 commit into from
Jan 9, 2023
Merged

Add User to README #787

merged 1 commit into from
Jan 9, 2023

Conversation

joocer
Copy link
Contributor

@joocer joocer commented Jan 2, 2023

Existing README welcomes PRs with additional users of this library - this PR adds a reference to Opteryx.

I also added a comma, I'm not sure if it was missing because of style or a typo but commas save lives so I added one.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 3823971501

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 85.941%

Totals Coverage Status
Change from base Build 3823674519: 0.0%
Covered Lines: 13185
Relevant Lines: 15342

💛 - Coveralls

@@ -93,7 +93,7 @@ $ cargo run --features json_example --example cli FILENAME.sql [--dialectname]
## Users

This parser is currently being used by the [DataFusion] query engine,
[LocustDB], [Ballista] and [GlueSQL].
[LocustDB], [Ballista], [GlueSQL], and [Opteryx].
Copy link
Contributor

Choose a reason for hiding this comment

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

@joocer thanks!

@alamb I don't think there are any standards around projects that use others, so I'm not sure if that's ok.

Anyway, maybe this session could be renamed to 'Acknowledgements'? Users seems a bit weird IMO

Copy link
Contributor

Choose a reason for hiding this comment

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

@AugustoFKL I don't think "Acknowledgements" is quite right as we are not really acknowledging assistance from other projects.

The point of this section, as I understand, is basically to encourage more use of the sqlparser crate by offering evidence that other projects have found it valuable enough to use.

Perhaps we could change the heading (in a different PR) to something like 'Powered By' to follow https://arrow.apache.org/powered_by/ ?

Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

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

Thank you @joocer -- this looks great to me.

but commas save lives so I added one.

😆

@@ -93,7 +93,7 @@ $ cargo run --features json_example --example cli FILENAME.sql [--dialectname]
## Users

This parser is currently being used by the [DataFusion] query engine,
[LocustDB], [Ballista] and [GlueSQL].
[LocustDB], [Ballista], [GlueSQL], and [Opteryx].
Copy link
Contributor

Choose a reason for hiding this comment

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

@AugustoFKL I don't think "Acknowledgements" is quite right as we are not really acknowledging assistance from other projects.

The point of this section, as I understand, is basically to encourage more use of the sqlparser crate by offering evidence that other projects have found it valuable enough to use.

Perhaps we could change the heading (in a different PR) to something like 'Powered By' to follow https://arrow.apache.org/powered_by/ ?

@alamb alamb merged commit 82cf554 into apache:main Jan 9, 2023
Ziinc pushed a commit to Logflare/sqlparser-rs that referenced this pull request Jan 20, 2023
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.

None yet

4 participants