The KDE Community develops and distributes open source software. That's okay! Join them first, see how things are done, mention your interest and where you'd like to work with. The best way to start contributing is to contact the community over Matrix, Telegram, IRCĪt first sight, it might seem a bit hard to interact in those groups. Help fund KDE projects with a one-off donation KDE is a commmunity creating free and open source software for desktop and portable computing. No screenshot of your desktop, use the Weekly Screenshot Thread instead.This subreddit is about the KDE community and not about stupid flamewars between open source projects. Post comparing various desktop environments and/or distros are not authorized on r/kde.This is a community subreddit so be respectful of other users.Blogs are fine as long as they have original content or add significant content to news or issue. No Spam, and please link to the source instead of blogs that link to the source.Reddit username in your phabricator/invent profile). KDE Dev Flair: To get a special flair that show your involvement within the KDE community, send a mod mail with a proof (e.g. Distros / Flair are in alphabetical order. Plasma 5.27: Discuss | /r/Linux Thread | /r/openSUSE Thread | /r/SteamDeck Threadĭistro Badges Flair: To get distro badges change your flair options above.Of course if I setup it to use the root user I have no problems in accessing it… Because some other kde apps share the same mysql server I would prefer digikam to be restricted at accessing only these to databases. However with this config I get an error at startup about CREATE and TRIGGER privileages not given to user… I checked the password and it is ok… Now I setup digikam to use these databases… GRANT ALL PRIVILEGES ON digikamthumbdb.* TO ‘digikamuser’ IDENTIFIED BY ‘password’ FLUSH PRIVILEGES GRANT ALL PRIVILEGES ON digikamdb.* TO ‘digikamuser’ IDENTIFIED BY ‘password’ FLUSH PRIVILEGES I created to databases in my mysql dikigamdb and digikamthumdb and grant all the privileages to some user digikamuser Finally, press the Migrate button to copy the data from SQLite to MySQL. Fill out the required fields as previously described, and use the Check DB Connection button to test the connection. Choose Tools | Database Migration, and select the MySQL item in the Type drop-down list in the right section. If you are already using digiKam with SQLite, you can use the database migration tool to move the existing data to MySQL databases. This can take a while if you have a lot of photos. Hit OK, and wait till digiKam populates the databases with data from photos. If everything works as it’s supposed to, switch to the Collections sections, and add the directories containing your photos. To check whether the database connection works properly, press the Check DB Connection button. Enter your MySQL user name and password in the appropriate fields. In the Schema Name field, enter the name of the database for storing photo metadata, and specify the name of the database for storing thumbnails in the Thumbnails Schema Name field. Select the MySQL item from the Type 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). There are two ways to switch digiKam from SQLite to MySQL. If you’ve just installed digiKam, and you haven’t yet added any collection to it, choose Settings | Configure digiKam, and switch to the Database section. And before you proceed, note the database connection information such as MySQL server address, user name, and password - you’ll need it when configuring MySQL settings in digiKam. You also have to create two MySQL databases: one for storing photo metadata (e.g., digikam) and the other for storing thumbnails (e.g., thumbnails-digikam). Obviously, to use digiKam with MySQL, you need a MySQL server. You can also use MySQL tools to back up and analyze digiKam’s data. This way, you can use multiple digiKam installations (e.g., on your notebook and desktop machine) to access and manage your photo collections. Of course, you might wonder why you’d want to switch to MySQL when SQLite already does a good job of managing the data? Using MySQL as digiKam’s database back-end allows you to store the data on a remote server. But the photo management application also provides support for the popular MySQL database engine, and it comes with a database migration tool that can help you to move your data from SQLite to MySQL. By default, digiKam uses SQLite as its back-end for storing important metadata and thumbnails.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |