Should you be migrating from another vendor, there may be constructs where GBQ differs.
For example, GBQ DATE is a DATE (as it is in many vendors, except say ORACLE/Exasol where it is really a timestamp).
Meanwhile GBQ TIMESTAMP is effectively a TIMESTAMP with TZ where values are stored at UTC, as some other vendors do.
While GBQ DATETIME is not stored at UTC.
Many of the operations to _add, _x_between etc, will be generated using the equivalent GBQ expressions where DATE, TIME and TIMESTAMP TZ are involved.
If you have further concerns, please contact support.
Generally, would recommend that you be using CA 11.1.4+, as it automatically generates SQL to compensate for GBQ limitations, which in several cases Google have since improved in their updates.
Similarly, be aware of the Google BigQuery JDBC driver, for example http://www.ibm.com/support/pages/node/6350937
Ideally, you would be using more current Google drivers, but should you be using older versions avoid http://www.ibm.com/support/pages/node/6350933
------------------------------
NIGEL CAMPBELL
------------------------------
Original Message:
Sent: Wed April 28, 2021 12:45 PM
From: Kay Vandevanter
Subject: Google BIGQUERY function not found: _ADD_DAYS
Here is a link to Google documentation related to this topic: https://cloud.google.com/bigquery/docs/reference/standard-sql/operators?hl=en_US#date_arithmetics_operators
We are recommending as we transition to GCP BigQuery that cognos developers will need to rewrite anything using date, datetime, time and timestamp functions.
------------------------------
Kay Vandevanter
------------------------------