4 ms·
+1. They'd have a much stronger case if they didn't drag in silly complaints such as "[Google BQ] does not support the ANSI SQL syntax of 'substring'. Need to c
by dhd415 10y ago
+1. They'd have a much stronger case if they didn't drag in silly complaints such as "[Google BQ] does not support the ANSI SQL syntax of 'substring'. Need to change to 'substr'".
- santoshalper 10y agoIt might seem petty, but I can't see how it hurt their case. If you're migrating hundreds of queries or reports from a local SQL environment to the cloud, being 100% query compatible is nice.
- twalk 10y ago+1
- twalk 10y agoKinda funny that a +1 with no verbiage is still rated. I will note I am enjoying reading these comments especially the ones that have real data points, real implementations and considerations of database structures/architectures on both of the products vs. gripes of the brands.
- mhw 10y agoOr automatically generated queries coming from third party tools you don't control...
- timv 10y agoI disagree. In order to run the benchmark they had to modify the SQL in it. I much prefer it when a benchmarking exercise is sufficiently transparent for another party to come along an replicate the result. That implies that they should provide details on all SQL changes that they made. Some of the phrasing was a little petty - BigQuery in “Legacy SQL” mode supports this but then joins don’t really work - but being clear about what they had to change seems totally appropriate to me.