Print

[xplicit]

While transfering my database I encountered a problem with my new phpmyadmin.

While using:

Code: [Select]

ALTER TABLE `cpg131_pictures` ADD `mtime` TIMESTAMP NOT NULL AFTER `hits` ;
I get the restult

Field    type                 atrr                   Null              default            Extra
mtime timestamp(14)                           YES             NULL

So it seems NOT NULL is not supported

Could this cause a problem in the future?




 

[artistsinhawaii]

I would suggest manually edit your Pictures table so that the Mtime field looks like:


Field                :    mtime
Type               :    timestamp
Collation           :
Attributes        :    ON UPDATE CURRENT_TIMESTAMP
Null                 :    No
Default            :    CURRENT_TIMESTAMP
Extra               :


Dennis

[xplicit]

Well uhmmm..... thats the point I always do such things manually but it doenst accept the settings

Original on my old server the statement was

`mtime` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,

But my new host (same version phpmyadmin) doesn't accept the CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP so I checked the original setup script which said  mtime timestamp(14) NOT NULL,

But will try severals things today to make it somehow correct, my concern at the moment is if this will cause a problem if I really cant change it

[Stramm]

the new phpmyadmin has a dropdown in export - 'SQL export compatibility' -> try setting it to MYSQL40

[xplicit]

Ok seems I got to live with it

Removed the complete picture table, exported my old one with compatiblility MYSQL40 but get same result while importing this at my new host.

I guesss I have to live with it

Will change my testing server to see what the effect will with the "wrong" settings

[Stramm]

try to remove   

Code: [Select]

AFTER `hits`