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

Promoted SQL's set-based advantages #268

Open
wants to merge 1 commit into
base: gh-pages
from

Conversation

@johnthomaswright
Copy link

@johnthomaswright johnthomaswright commented Oct 22, 2018

SQL's set-based syntax is different for those who have only been exposed to iterative programming languages, particularly those reading and writing to delimited text files. SQL creates more concise, self-describing ways to model, relate, and aggregate data.

SQL's set-based syntax is different for those who have only been exposed to iterative programming languages, particularly those reading and writing to delimited text files.  SQL creates more concise, self-describing ways to model, relate, and aggregate data.
Copy link
Contributor

@remram44 remram44 left a comment

Hi @johnthomaswright, thanks for the contribution! I'm with you, I think it makes sense to make it clear what SQL is about. However I am not sure about "set-based language".

@@ -12,6 +12,7 @@ keypoints:
- "A relational database stores information in tables, each of which has a fixed set of columns and a variable number of records."
- "A database manager is a program that manipulates information stored in a database."
- "We write queries in a specialized language called SQL to extract information from databases."
- "SQL is a set-based language, where we specify what data and format to return or save; but not how to save it or how to retrieve it (like you would specify in iterative loops in other languages.)

This comment has been minimized.

@remram44

remram44 Oct 26, 2018
Contributor

Maybe "query-based" language instead? "set" usually refers to unordered collections.

This comment has been minimized.

@jttkim

jttkim Oct 26, 2018

Considering that a relation is defined to be a set of tuples, "set based language" is accurate.

Queries are surely a central part of SQL, but there's also data manipulation, as well as data definition. Sets (or relations) are the the unifying theme, as all defining, manipulating and querying pertains to relations at the end of the day.

This comment has been minimized.

@henrykironde

henrykironde Dec 2, 2019
Contributor

I would also recommend using query rather than set

@johnthomaswright
Copy link
Author

@johnthomaswright johnthomaswright commented Oct 26, 2018

@henrykironde
Copy link
Contributor

@henrykironde henrykironde commented Oct 26, 2018

How about something like
SQL is a query-based language, where we specify what data and format to return or save; and it's the work of the database manager to plan on how to save the data or how to retrieve the data.

@johnthomaswright
Copy link
Author

@johnthomaswright johnthomaswright commented Oct 26, 2018

fmichonneau pushed a commit to fmichonneau/sql-novice-survey that referenced this pull request Nov 1, 2019
util.py: make functions return NotImplemented
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.