upgrading from 3.0 to 3.3

[Thomas Spuhler]

On Wednesday, November 19, 2014 08:36:31 AM you wrote:
> Hi,
> INNODB is a engine.
> So, the egine statement has to be on the create statement.
> So do,
> 
> 1.) show tables;
> 
> 
> For e.g table cache:
> (look at the last line with "ENGINE".)
> 
> 2.) show create table cache;
> 
> +-------+-----------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------+
> | Table | Create
> 
> Table
> 
> +-------+-----------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------+
> | cache | CREATE TABLE `cache` (
> 
>   `user_id` int(10) unsigned NOT NULL,
>   `cache_key` varchar(128) CHARACTER SET ascii NOT NULL,
>   `created` datetime NOT NULL DEFAULT '1000-01-01 00:00:00',
>   `expires` datetime DEFAULT NULL,
>   `data` longtext NOT NULL,
>   KEY `expires_index` (`expires`),
>   KEY `user_cache_index` (`user_id`,`cache_key`),
>   CONSTRAINT `user_id_fk_cache` FOREIGN KEY (`user_id`) REFERENCES
> `users` (`user_id`) ON DELETE CASCADE ON UPDATE CASCADE
> ) ENGINE=InnoDB DEFAULT CHARSET=utf8 |
> +-------+-----------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------------
> --------+
> 
> 
> And so on.
> 
> Rgds.
> 
> Franz
> 
> 1 row in set (0.03 sec)Am 19.11.14 um 01:27 schrieb Thomas Spuhler:
> > On 11/18/2014 04:31 PM, Torsten Grote wrote:
> >> mysql -h localhost -u roundcube -p
> > 
> > no problem
> > $ mysql -h localhost -u roundcube -p
> > Enter password:
> > Welcome to the MariaDB monitor.  Commands end with ; or \g.
> > Your MariaDB connection id is 52
> > Server version: 10.0.14-MariaDB Mageia MariaDB Server
> > 
> > Copyright (c) 2000, 2014, Oracle, SkySQL Ab and others.
> > 
> > Type 'help;' or '\h' for help. Type '\c' to clear the current input
> > statement.
> > 
> > MariaDB [(none)]>
> > 
> > 
> > Just a thought: The procedure refers to INNODB
> > How can I check for certain, if my mariadb uses the INNODB engine?
> > 
> > Thomas
> > 
> > 
> > _______________________________________________
> > users mailing list
> > users at lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users

Thanks a lot. I found some ERROR messages in the logs  Innodb section of our mariadb. Let the 
maintainer solve this issue first.

-- 
Best regards
Thomas Spuhler

All of my e-mails have a valid digital signature
ID 60114E63
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20141120/2493f627/attachment.sig>