![]() Specify the name of the second database for storing wavelets compressed thumbnails in the Thumbs Db Name field. In the Core Db Name field, enter the name of the first database for storing photo metadata. and then under Settings section, select MySQL Server from the drop down list.Įnter the IP address of your MySQL server in the Host Name field and specify the correct port in the Port field (the default port is 3306). Now, in digiKam, go to Settings → Configure digiKam. If you have an enormous collection, you should start the MySQL server with mysql -max_allowed_packet = 128M and then under Settings section, select a database from the drop down list. To switch from SQLite to MySQL database, go to Settings / Configure digiKam. You can also use MySQL tools to backup and analyze digiKam’s data. This way, you can use multiple digiKam installations (For instance,on your notebook and PC) to access and manage your photo collections. Using MySQL as digiKam’s database back-end allows you to store the data on a remote server. Local, to replace the local SQLite storage and latter, to use a shared computer through network. Using MySQL as digiKam’s database back-end allows you to store the data on local as well as remote server. With such large collections, SQLite introduces latency which slows down the application. Of course, you might wonder why you’d want to switch to MySQL when SQLite already does a good job of managing the data? MySQL offers many advantages for storing digiKam data, especially when collections include more than 100,000 items. MariaDB development is more open and vibrant.ĭigiKam also provides support for popular MySQL database engine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |