An error occurred fetching the project authors.
- 11 Jun, 2020 2 commits
-
-
Alain Takoudjou authored
-
Alain Takoudjou authored
-
- 29 Apr, 2020 1 commit
-
-
Jérome Perrin authored
Mariadb was not shared, because installing mroonga writes a plugin in mariadb's plugin dir and it's not allowed for one part to write in another part's folder. The approach is to install mroonga plugin in it's own plugin directory, then copy all mariadb default plugins in this plugin directory and configure instance to use mroonga's plugin directory. Groonga also has plugins and we are using groonga-normalizer-mysql plugin. Fortunately, groonga reads plugins located in paths listed in GRN_PLUGINS_PATH environment variable, so we can use a simpler approach of installing plugins in their own installation folder and set GRN_PLUGINS_PATH in the environment of processes using groonga, ie. the mariadb server process.
-
- 02 Oct, 2019 1 commit
-
-
Jérome Perrin authored
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
-
- 26 Jul, 2019 1 commit
-
-
Vincent Pelletier authored
Auto-compute a value suitable for the number of requested Zope processes and threads for default ERP5 needs.
-
- 23 Jul, 2019 2 commits
-
-
Alain Takoudjou authored
-
Alain Takoudjou authored
-
- 04 Jun, 2019 1 commit
-
-
Julien Muchembled authored
Since we moved to MariaDB 10.3, that's actually already the case because of --plugin-maturity=gamma
-
- 07 Sep, 2018 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 08 Feb, 2017 1 commit
-
-
Vincent Pelletier authored
-
- 10 Aug, 2016 1 commit
-
-
Vincent Pelletier authored
-
- 20 May, 2016 1 commit
-
-
Vincent Pelletier authored
This allows enabling replication later without requiring a mariadb restart. For now, nothing passes the internal server-id instance parameter, so replication is not.
-
- 17 Dec, 2015 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 23 Apr, 2014 1 commit
-
-
Vincent Pelletier authored
MySQL changed the default value 3 times since 5.1, causing a waste of disk space when recreating schemas (tables move out of an already large system tablespace, which cannot be easily reclaimed). Also, per-table option fragments free space: if a table shrinks, freed space cannot be used by another table without recreating shrunk table (which induces at least a write-lock during data copy, which may not be trivial).
-
- 05 Apr, 2014 1 commit
-
-
Vincent Pelletier authored
Check got removed from code, comment lingers on.
-
- 20 Mar, 2014 1 commit
-
-
Vincent Pelletier authored
-
- 05 Feb, 2014 1 commit
-
-
Vincent Pelletier authored
-
- 04 Sep, 2013 1 commit
-
-
Julien Muchembled authored
It is useful to temporary enable such settings while preparing an instance.
-
- 08 Aug, 2013 2 commits
-
-
Vincent Pelletier authored
-
Julien Muchembled authored
-
- 16 Jul, 2013 3 commits
-
-
Vincent Pelletier authored
Better failing than silently ignoring a missing parameter because of a typo. Only parameters provided by users should be allowed to be missing, not internal ones.
-
Vincent Pelletier authored
Also, follow naming convention.
-
Vincent Pelletier authored
-