@ajb5d Thanks for the message, and good question! Either/both would be appreciated. We're using BigQuery a lot at the moment, especially at datathons, so a BigQuery version would definitely get some use.

We don't have a good system for managing different dialects of SQL, so we'd welcome your suggestions for this. With MIMIC we have ended up with two separate branches (google-cloud-views for BigQuery and master for Postgres), which isn't ideal.

Would it be reasonable make a directory for each dialect and keep them on the same branch?

Also, Are you opposed to a Postgres user-defined function? I'm having trouble finding an elegant way to cast a string to integer in a "safe" way.

Would it be reasonable make a directory for each dialect and keep them on the same branch?

I think this probably easier to navigate than separate branches, so sounds good to me.

Also, Are you opposed to a Postgres user-defined function? I'm having trouble finding an elegant way to cast a string to integer in a "safe" way.

Also sounds good to me!

Sorry I haven't reviewed the PR yet, but hopefully I will find time to soon!