![]() ![]() If the database link appears again, digiKam continues it's work. Press the "Migrate ->" button and enjoy the progress on the bottom of the dialogġ) If the connection is down, digiKam stops its database actions, and tries to reconnect.As target (right side) type in your MySQL database connection database.As source (left side) select your SQLite database.go to the migration dialog (Tools -> Database Migration).To copy your SQLite data to your MySQL database do the following: press "Check connections" - A dialog should show you, that the connection could be established with the current settings.only check the "Internal Server" checkbox this mode works like the internal akonadi database server mode (thanks goes to the akonadi people - great work!), but has a little bit improved > use an internal database management server > use an existing database management server where you have created a dedicated account at the database type combobox, choose QMYSQL as backend.go to the database settings (Settings -> Configure Digikam -> Database).The dedicated branch is located at this url from KDE svn repositoryĪssume you compiled your version and would like to test digikam:Īfter the first start, your existing database settings will be converted to an extended format.Īfter that, your are using digiKam in SQLite mode, it should work like before (from users point of view). (For the last point: If you are not yet familiar on how to test current development code, this page gives you a short introduction how to get and compile digiKam from source.įor reporting bugs please use the normal KDE bug tracker. To have the future right now and you are able to compile your version by yourself: You are the right person :) ![]() So if you are brave enough to crash your whole existing database structure (images are not touched), have a little amount of free time or you would like ![]() in a dedicated branch), the most bugs are possible undiscovered. add possibiliy to start an own database serverīecause only a few persons trying out this work (which resides atm.adding a solution for migrating from SQLite to MySQL and vice versa.Last summer I saw bug #127321 an thought, this can be done by me (partly at least).Īfter some (successful) prototypic implementation, most of the time where spent into smooth integration in the existing ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |