This is because UTC is not affected by DST, in effect CST becomes UTC -.
Using bind variables also improves query performance in the database, eliminates the need for special handling of literal quotation marks in the input, and protects against SQL injection attacks.
If you attempt to change the availability you get the following error message: “Updating the availability section of a Dataset is not supported.
Existing availability configuration: Frequency=Day, Interval=1, Anchor Date Time=01/01/0001 , Offset=, Style=Start Of Interval, new availability configuration: Frequency=Day, Interval=1, Anchor Date Time=01/01/0001 , Offset=, Style=Start Of Interval.” Take Daylight Savings Time for example, you want to run your datasets at midnight CST (UTC -) but during DST it becomes am CST.
The GVAR interface file including the updated data: Click here to download an example GVAR interface file containing the latest version of the GVAR dataset (1979Q2-2016Q4) together with the corresponding trade flows file.
Usage: datacube dataset update [OPTIONS] [DATASETS]... Update datasets in the Data Cube Options: --allow-any TEXT Allow any changes to the specified key (a.b.c) -r, --match-rules PATH Rules to be used to associate datasets with products -t, --dtype TEXT Product to be associated with the datasets -a, --auto-match Automatically associate datasets with products by matching metadata --dry-run Check if everything is ok -h, --help Show this message and exit. Or is give any indication as to what aspects of Dataset are meant to be immutable and which can be safely changed.