Re: DB help needed to solve issue with pimitemtable
Erik Quaeghebeur <[email protected]>
| Newsgroups | gmane.comp.kde.users.pim |
|---|---|
| Message-ID | <[email protected]> |
On dinsdag 11 december 2018 22:59:17 CET, Pablo Sanchez wrote: > What version of MySQL do you have? > > SHOW VARIABLES LIKE "%version%"; ERROR 1146 (42S02): Table 'performance_schema.session_variables' doesn't exist But it should be mysql-5.7.24 if I can believe the mysql shell startup text and my package manager: 5.7.24(0/18)(22:57:44 20-11-18)(server -cjk -client-libs -cracklib -debug -experimental -jemalloc -latin1 -libressl -numa -perl -profiling -selinux -static -static-libs -systemtap -tcmalloc -test -yassl … But perhaps I should enable some of those flags with a - in front? This is possibly related to something I asked about a good two years ago: https://marc.info/?l=kdepim-users&m=147643533119190&w=2 https://marc.info/?l=kdepim-users&m=147643533119190&q=p3 > Please quote the objects ... > > ALTER TABLE `pimitemtable` ALTER `atime` SET DEFAULT current_timestamp(); ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'current_timestamp()' at line 1 > Now, if that doesn't work, please try this: > > ALTER TABLE `pimitemtable` MODIFY `atime` > timestamp NOT NULL DEFAULT current_timestamp(); Query OK, 0 rows affected (0,17 sec) Records: 0 Duplicates: 0 Warnings: 0 And in the show create table pimitemtable; result I see `atime` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, > and just for grins: > > SELECT CURRENT_TIMESTAMP(); +---------------------+ | CURRENT_TIMESTAMP() | +---------------------+ | 2018-12-11 23:06:45 | +---------------------+ 1 row in set (0,00 sec) And… mysql> alter table pimitemtable modify column remoteId varbinary(1024); Query OK, 43524 rows affected (1,98 sec) Records: 43524 Duplicates: 0 Warnings: 0 Hurray! Cheers, Erik