[prev in list] [next in list] [prev in thread] [next in thread] 

List:       owncloud
Subject:    Re: [Owncloud] switching from sqlite to mysql
From:       Frank Karlitschek <frank () owncloud ! org>
Date:       2014-01-15 21:41:30
Message-ID: A273A298-F7CC-49D0-BE67-99B50F7048A7 () owncloud ! org
[Download RAW message or body]

We are working on providing a DB migration script. Here is a pull request t=
hat is still work in progress:
https://github.com/owncloud/core/pull/6457
Any help with coding and testing is highly appreciate.


Frank


On 15.01.2014, at 16:17, Otto Kek=E4l=E4inen <otto@seravo.fi> wrote:

> I tried this migration a few days ago (look at the mailing list
> history with author my name), and I after manually fixing many many
> things I eventually gave up. At the moment there is no working
> migration script.
> =

> Today I reinstalled one OwnCloud installation with MySQL and simply
> re-created the users and moved the files. A bit of work, but at the
> moment the best option. Hopefully an official migration script would
> be made at some point. Even better if SQLite was not default, not even
> for home users..
> =

> 2014/1/15 Reinoud van Leeuwen <reinoud.v@n.leeuwen.net>:
>> =

>> On 15 jan. 2014, at 21:56, Diederik de Haas <didi.debian@cknow.org> wrot=
e:
>> =

>>> On Wednesday 15 January 2014 21:39:19 Reinoud van Leeuwen wrote:
>>>> I have another problem: it seems that in my SQLite installation a table
>>>> oc_fscache is present, which is missing in the Mysql Dump...
>>> =

>>> Just create that table, or leave it out all together. It is meant to ca=
che
>>> things, so if it's not present, it will be created (and filled).
>>> I've cleared that table many times during testing, so afaik it's safe t=
o leave
>>> it out.
>> =

>> Next thing I stumble upon is:
>> =

>> ERROR 1062 (23000) at line 5269: Duplicate entry 'calendar/appinfo/remot=
e.php-core' for key 'PRIMARY'
>> =

>> Makes sense since the create table statement is
>> =

>> CREATE TABLE `oc_appconfig` (
>>  `appid` varchar(32) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
>>  `configkey` varchar(64) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
>>  `configvalue` longtext COLLATE utf8_unicode_ci,
>>  PRIMARY KEY (`appid`,`configkey`),
>> =

>> and in the dump are lines:
>> =

>> INSERT INTO `oc_appconfig` VALUES('calendar/appinfo/remote.php','core','=
remote_calendar');
>> INSERT INTO `oc_appconfig` VALUES('calendar/appinfo/remote.php','core','=
remote_caldav');
>> =

>> =

>> So, someone might know how to fix this particular problem, but my point =
is that from a application maintainer perspective I do not feel really good=
 having to hack like this in SQL dumps to get this working. And it sounds l=
ike the database is different on SQLite, otherwise this would not have been=
 present in the database at all..
>> Or is this the result from buggy updates?
>> =

>> Reinoud
>> _______________________________________________
>> Owncloud mailing list
>> Owncloud@kde.org
>> https://mail.kde.org/mailman/listinfo/owncloud
> =

> =

> =

> -- =

> Otto Kek=E4l=E4inen
> +358 44 566 2204
> http://seravo.fi/
> _______________________________________________
> Owncloud mailing list
> Owncloud@kde.org
> https://mail.kde.org/mailman/listinfo/owncloud

_______________________________________________
Owncloud mailing list
Owncloud@kde.org
https://mail.kde.org/mailman/listinfo/owncloud
[prev in list] [next in list] [prev in thread] [next in thread]