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

quotations for strings #184

Open
wtong5456 opened this Issue Aug 8, 2017 · 2 comments

Comments

Projects
None yet
4 participants
@wtong5456

wtong5456 commented Aug 8, 2017

In module 3 'Filtering' it is worth mentioning that either single or double quotation marks can be used in queries. I.e. SELECT * FROM Visited WHERE site='DR-1'; or SELECT * FROM Visited WHERE site="DR-1"; can be used.

@pgmccann

This comment has been minimized.

Contributor

pgmccann commented Aug 22, 2017

This is not universal across database managers - in PostgreSQL only single quotes can be used to specify string values by which to filter (double quotes can be used to create and refer to case-sensitive table and column names) - I believe this is in accordance with the ANSI SQL standard. I would suggest that the use of single quotes be at least encouraged here.

rgaiacs added a commit to rgaiacs/swc-sql-novice-survey that referenced this issue Apr 17, 2018

Merge pull request swcarpentry#184 from rgaiacs/styles-js-load-images
Replace extract_figures.py with Javacript
@danmichaelo

This comment has been minimized.

Contributor

danmichaelo commented Oct 12, 2018

Agree, we should encourage single quotes even though double quotes works. The SQLite FAQ also does this:

Use single-quotes, not double-quotes, around string literals in SQL. This is what the SQL standard requires.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment