Commit 0b377eb4 authored by Jérome Perrin's avatar Jérome Perrin

erp5: set mariadb timezone to UTC

ERP5Catalog assumes that dates in catalog are UTC, this works
fine with DATETIME columns that does not carry any timezone
information, but TIMESTAMP columns are converted to mariadb timezone,
which is by default system timezone.

If we want ERP5Catalog to query on TIMESTAMP columns with the existing
logic of converting dates to UTC (because "dates are in UTC in
catalog"), we need to have TIMESTAMP columns in UTC.

This also generally seem a better default than falling back to system
timezone.

/reviewed-on nexedi/slapos!623
parent 81870136
......@@ -42,7 +42,7 @@ md5sum = d32417746fcf671d4e86a70379815039
[template-my-cnf]
filename = my.cnf.in
md5sum = 5a6f337117ba8b72d7fe3b7a9f26f5f6
md5sum = 771bfd921aa5e59e1b4712ba113fa84b
[template-mariadb-initial-setup]
filename = mariadb_initial_setup.sql.in
......
......@@ -29,6 +29,8 @@ max_allowed_packet = 128M
query_cache_size = 32M
innodb_file_per_table = {{ parameter_dict['innodb-file-per-table'] }}
default_time_zone = '+00:00'
plugin_load = ha_mroonga
max_connections = {{ parameter_dict['max-connection-count'] }}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment