BigQuery SQL improvements

GoogleCodeExporter commented 8 years ago

We are planning a significant update to BigQuery's SQL dialect to address a 
number of user issues and feature suggestions. If your bug was merged into this 
issue, then we anticipate that this update will address your issue.

Further details to be announced here soon!

Original issue reported on code.google.com by jcon...@google.com on 24 Feb 2016 at 4:52

GoogleCodeExporter commented 8 years ago

Issue 447 has been merged into this issue.

Original comment by jcon...@google.com on 24 Feb 2016 at 4:53

GoogleCodeExporter commented 8 years ago

Issue 425 has been merged into this issue.

Original comment by jcon...@google.com on 24 Feb 2016 at 4:56

GoogleCodeExporter commented 8 years ago

Issue 424 has been merged into this issue.

Original comment by jcon...@google.com on 24 Feb 2016 at 4:59

GoogleCodeExporter commented 8 years ago

Issue 415 has been merged into this issue.

Original comment by jcon...@google.com on 24 Feb 2016 at 5:01

GoogleCodeExporter commented 8 years ago

Issue 39 has been merged into this issue.

Original comment by jcon...@google.com on 26 Feb 2016 at 4:35

GoogleCodeExporter commented 8 years ago

Issue 374 has been merged into this issue.

Original comment by jcon...@google.com on 26 Feb 2016 at 10:30

GoogleCodeExporter commented 8 years ago

Issue 359 has been merged into this issue.

Original comment by jcon...@google.com on 26 Feb 2016 at 10:53

GoogleCodeExporter commented 8 years ago

Issue 336 has been merged into this issue.

Original comment by jcon...@google.com on 26 Feb 2016 at 10:55

GoogleCodeExporter commented 8 years ago

Issue 350 has been merged into this issue.

Original comment by jcon...@google.com on 26 Feb 2016 at 10:58

GoogleCodeExporter commented 8 years ago

Issue 340 has been merged into this issue.

Original comment by jcon...@google.com on 26 Feb 2016 at 11:03

GoogleCodeExporter commented 8 years ago

Issue 325 has been merged into this issue.

Original comment by jcon...@google.com on 29 Feb 2016 at 11:52

GoogleCodeExporter commented 8 years ago

Issue 289 has been merged into this issue.

Original comment by jcon...@google.com on 29 Feb 2016 at 11:58

GoogleCodeExporter commented 8 years ago

Issue 194 has been merged into this issue.

Original comment by jcon...@google.com on 1 Mar 2016 at 12:21

GoogleCodeExporter commented 8 years ago

Issue 121 has been merged into this issue.

Original comment by jcon...@google.com on 1 Mar 2016 at 7:57

GoogleCodeExporter commented 8 years ago

Issue 56 has been merged into this issue.

Original comment by jcon...@google.com on 1 Mar 2016 at 8:12

GoogleCodeExporter commented 8 years ago

Issue 351 was closed as 'fixed' two days ago, but it is not, in fact, fixed. 
Should it be merged into this issue instead? If not, could you reopen issue 351?

Original comment by oliver.u...@gmail.com on 3 Mar 2016 at 10:04

GoogleCodeExporter commented 8 years ago

I replied on that issue. The SQL dialect fixes will address the error message 
as well, but for the most part I think we can consider issue 351 to be fixed 
independently.

Original comment by jcon...@google.com on 4 Mar 2016 at 10:34

GoogleCodeExporter commented 8 years ago

Issue 467 has been merged into this issue.

Original comment by ada...@google.com on 18 Mar 2016 at 7:31

GoogleCodeExporter commented 8 years ago

Issue 474 has been merged into this issue.

Original comment by jcon...@google.com on 21 Mar 2016 at 6:45

GoogleCodeExporter commented 8 years ago

Issue 379 has been merged into this issue.

Original comment by jcon...@google.com on 5 Apr 2016 at 5:54

runt18 / google-bigquery

BigQuery SQL improvements #448