~joec or ~cypheon, could you kindly make these changes to a new version of chores compatible with Nextcloud 29? This would make it possibel for many more people to use chores - and believe me, the functionality is needed and appreciated!
Comment by ~cypheon on ~cypheon/nextcloud-chores
Hi Menelic,
thanks for your interest in the app and the kind words! I have uploaded the current version 0.0.5 to the stable channel. Since I'm happy (and surprised) that someone besides me has a use for this app, please let me know if you discover any bugs or missing basic features.
Thanks and best regards, Johann
REPORTED
RESOLVED IMPLEMENTED~cypheon assigned ~cypheon to #3 on ~cypheon/nextcloud-chores
Comment by ~cypheon on ~cypheon/nextcloud-chores
Version "10.x" probably means it's a MariaDB (that would explain that error). To verify you can run
SHOW VARIABLES LIKE 'version_comment';
to get the exact variant info.
Comment by ~cypheon on ~cypheon/nextcloud-chores
Hi, the issue seems to be related to either MariaDB or an older MySQL version not supporting the timezone offset that is appended when storing values in the DB. MySQL supports this since version 8.0.19, MariaDB unfortunately doesn't (see comments at the end of https://jira.mariadb.org/browse/MDEV-11576 ). Is it an option for you to switch to a version of MySQL >= 8.0.19? (I understand if it's not, since depending on the since of your Nextcloud instance this could be quite a major undertaking.)
~cypheon assigned ~cypheon to #2 on ~cypheon/nextcloud-chores
Comment by ~cypheon on ~cypheon/nextcloud-chores
Hi, with a MariaDB/MySQL DB I was able to reproduce the issue, with a small change I could provide the missing default value that the DBMS complains about.
I just released a 0.0.4 nightly version that should fix the issue. Please let me know if you run into other issues or not-implemented use cases :)
REPORTED
RESOLVED FIXEDComment by ~cypheon on ~cypheon/nextcloud-chores
Hi, thank you for the detailed error description! I'll have a look at this during the week and provide an updated version. The fix is probably something simple like adding a default value to a query... Are you using MySQL? Until now, I only tested with Postgres so I suspect it's something DBMS-sepcific...