Issue Description

Since the old Instagram API will stop working on June 29 (See https://www.instagram.com/developer/), the url in https://github.com/parse-community/parse-server/blob/d0a9c709fea4cbdba540420353a36a0e89601ffb/src/Adapters/Auth/instagram.js#L9 needs to be changed to match the new "instagram_graph_user_profile" API. (See https://developers.facebook.com/docs/instagram-basic-disp

Hi, First and foremost, I think this is a great start at making something really simple and effective. Thank you!!

However... I have always found template strings a little odd especially in this context.
Let us say we have

const query = `SELECT ${distinct}, ${columns} FROM ${table} ${innerJoins} WHERE ${where}`;
(Where distinct, columns, table etc are their own strings made up of other

See the-road-to-graphql/fullstack-apollo-express-postgresql-boilerplate#5 for users domain. Maybe someone wants to add tests for the messages domain too.

Feature request:

Select builders are often used in sub query with aliases.
It would be a nice syntax addition if instead of using an object we could output the builder with a alias directly thanks to an as method

//currently 
sh.select().from({
  as:'foo',
  value:sh.select().from('users').where('age','>',42).noop()
});

could be written:

sh.sele

I ran into your lambda today an managed to deploy it. Everything seems to work fine under normal circumstances, but I encounter an error when i try to change the output format (I tried -Fp and --format=plain).
When using the PGDUMP_ARGS to change the output format, I get the following exception:

"Error: pg_dump gave us an unexpected response".
I've looked through the code and this seems t