Skip to content

Fixed Typo and modification date #7

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
May 24, 2019
Merged

Conversation

whitten
Copy link
Contributor

@whitten whitten commented May 23, 2019

The previous version had "non-standar Informix" instead of "non-standard Informix"

I'm also curious about the need for the Informix paragraph as the

The document http://informixsoftware.com/ids117/Guide%20to%20SQL%20Tutorial%20Version%20117.pdf
says:
Earlier versions of the database server supported only the IBM Informix extension
to the ANSI-SQL standard syntax for outer joins. This syntax is still supported.
However, the ANSI-SQL standard syntax provides for more flexibility with creating
queries. It is recommended that you use the ANSI-SQL standard syntax to create
new queries. Whichever form of syntax you use, you must use it for all outer joins
in a single query block.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
The previous version had "non-standar Informix" instead of "non-standard Informix"

I'm also curious about the need for the Informix paragraph as the 

The document http://informixsoftware.com/ids117/Guide%20to%20SQL%20Tutorial%20Version%20117.pdf  
says:
Earlier versions of the database server supported only the IBM Informix extension
to the ANSI-SQL standard syntax for outer joins. This syntax is still supported.
However, the ANSI-SQL standard syntax provides for more flexibility with creating
queries. It is recommended that you use the ANSI-SQL standard syntax to create
new queries. Whichever form of syntax you use, you must use it for all outer joins
in a single query block.
@jleffler jleffler merged commit e72dbf4 into ronsavage:master May 24, 2019
@jleffler
Copy link
Collaborator

Thank you for fixing the typo.

The Informix OUTER JOINS paragraph is not necessary if you're coming from anything other than an Informix background. For those of who have worked with Informix, it might be useful to have the information available — it took some effort to create and this was a simple way to make the information available more widely. So, it is entirely optional whether you pay any attention to it. It serves a purpose for me; it may not help anyone else. It certainly isn't a recommendation that any other DBMS should support the Informix OUTER notation; the Standard notations are superior.

ronsavage pushed a commit that referenced this pull request Mar 15, 2020

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
…verlaps_predicate

[fix]alter <overlaps predicate part> to <overlaps predicate>
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

2 participants