-
Notifications
You must be signed in to change notification settings - Fork 22
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
adding initial draft of Quick SQL Tricks Guide #319
base: master
Are you sure you want to change the base?
Conversation
hey @ohasselblad - let me know what you think of this initial draft and if I should add anything :) Wondering if I should explain the WHERE operator? Casting? Alias? Etc? |
|
||
The 'DB' part of CartoDB means that it is built on a database called [PostgreSQL](https://www.postgresql.org/docs/9.5/static/index.html). PostgreSQL's programming language is SQL, an acronym for structured query language, which is a powerful and popular language for analyzing tables of data. This reference guide provides several SQL queries and operations that you can easily use as part of your data analysis workflow. If you are new to SQL, first review lesson one of this series, [SQL and PostGIS in CartoDB Editor](https://academy.cartodb.com/courses/sql-postgis/intro-to-sql-and-postgis/). | ||
|
||
## Basic Math Queries |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to have an example dataset that you can use the whole way so people can follow along and produce some of the results.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, let me search the Data Library for an appropriate dataset
Nice list, @michellechandra 👍 A few thoughts:
|
Was going to not review anything PostGIS related, would there be a way to discuss the geography type using just a SQL query that would be relevant? Or should that be saved for a different guide that is PostGIS tricks? |
Good point, let's do a different guide on PostGIS |
cc @ohasselblad