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

Add known issues section #40

Merged
merged 4 commits into from
Mar 25, 2024
Merged

Add known issues section #40

merged 4 commits into from
Mar 25, 2024

Conversation

hab6
Copy link
Contributor

@hab6 hab6 commented Mar 25, 2024

Add Known Issues section to the Readme including information about Superset problem 27427

Copy link
Member

@clach04 clach04 left a comment

Choose a reason for hiding this comment

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

Content great. Formatting changes needed

README.md Outdated
Comment on lines 239 to 240
Apache Superset issue [27427](https://github.com/apache/superset/issues/27427)
The Apache Superset SQL parser is able to recognize and handle row limiting clauses that use keywords **LIMIT** and **TOP** but does not handle the **FETCH FIRST** clause, which is used by some databases, including Ingres and PostgreSQL. If a **FETCH FIRST** clause is used in a SQL statement and the Superset config parameter **SQL_MAX_ROW** is set to a value > 0, the Superset parser appends a **LIMIT** clause to the SQL statement, making it syntactically invalid. This errant behavior can be seen when working with SQL statements and table metadata in Superset SQL Lab and may occur in other Superset operations as well. It is important to note that this is a problem with Apache Superset and not with the SQLAlchemy-Ingres connector.
Copy link
Member

Choose a reason for hiding this comment

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

This looks run on. The content is great! See https://github.com/ActianCorp/sqlalchemy-ingres/tree/hab6-add-known-issues#known-issues for what I mean.

Bare minimum change would be paragraph breaks:

  1. one after first line
  2. another one before the last line.

With those changes the markdown will be more clear. The text it self will be long in plain text so could benefit from some newlines but that's not a deal-breaker.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you for the suggestions! I added a few newlines. Hopefully it looks better now!

@clach04 clach04 merged commit 1a1cf07 into master Mar 25, 2024
@hab6 hab6 deleted the hab6-add-known-issues branch March 25, 2024 19:07
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