Re: DB help needed to solve issue with pimitemtable

Erik Quaeghebeur <[email protected]>
Newsgroups gmane.comp.kde.users.pim
Message-ID <[email protected]>
Dear Pablo,


Great to have you respond so quickly; thanks!

On dinsdag 11 december 2018 20:22:37 CET, Pablo Sanchez wrote:
>
> When are you getting the error?

When I tried to alter the length of the remoteId column.

> In MySQL, you can show the table's DDL:
>
>     show create table pimitemtable;

Cool. Below, I list those columns that differ (even cosmetically):

>   `rev` int(11) NOT NULL DEFAULT 0,

  `rev` int(11) NOT NULL DEFAULT '0',

Cosmetic? Seems strange to have a string default for an int.

>   `datetime` timestamp NOT NULL DEFAULT current_timestamp(),

  `datetime` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,

Cosmetic?

>   `atime` timestamp NOT NULL DEFAULT current_timestamp(),

  `atime` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',

I guess we see here what the problem is. How should I change this. How did 
this come to be?

>   `size` bigint(20) NOT NULL DEFAULT 0,

  `size` bigint(20) NOT NULL DEFAULT '0',

Cosmetic? Seems strange to have a string default for an int.

> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

) ENGINE=InnoDB AUTO_INCREMENT=257761 DEFAULT CHARSET=utf8


Best,

Erik
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.