[digikam] [Bug 350574] MIGRATION: MySQL to SQLite fails [patch]

https://bugs.kde.org/show_bug.cgi?id=350574 --- Comment #11 from Richard Mortimer --- (In reply to caulier.gilles from comment #10) > Richard, > > Swati has proposed a simple patch for this file. Any viewpoint about ? > > Gilles Caulier I've been discussing the

[digikam] [Bug 339607] MYSQL : Images not show if corresponding ImageInformation entry does not exist in database

https://bugs.kde.org/show_bug.cgi?id=339607 --- Comment #6 from Richard Mortimer --- Sorry. Had missed this one. I cannot see an obvious reason why there would be a difference between SQLite and MySQL. It should be easy to test the queries from the commandline in both

[digikam] [Bug 325655] MIGRATION : after MySQL to Sqlite database conversion, random tags are assigned to new images

https://bugs.kde.org/show_bug.cgi?id=325655 Richard Mortimer changed: What|Removed |Added CC|

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #80 from Richard Mortimer --- The only thing that I am aware of that potentially needs addressing in MySQL is the TagsTree support. I did note that there were some other issues addressing that so it may already

[digikam] [Bug 237878] SCHEMA : add foreign keys support

https://bugs.kde.org/show_bug.cgi?id=237878 --- Comment #15 from Richard Mortimer --- Yes. I think this can now be considered resolved. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 365354] Application crash on scanning for faces in large picture set.

https://bugs.kde.org/show_bug.cgi?id=365354 --- Comment #8 from Richard Mortimer --- I'm concerned that increasing the max packet size is only hiding the problem and not curing the real problem. A similar error is also reported for SQLite so that would need an

[digikam] [Bug 365354] Application crash on scanning for faces in large picture set.

https://bugs.kde.org/show_bug.cgi?id=365354 Richard Mortimer changed: What|Removed |Added CC|

[digikam] [Bug 283323] MYSQL : a new label "_Digikam_root_tag_" is created every time

https://bugs.kde.org/show_bug.cgi?id=283323 --- Comment #76 from Richard Mortimer --- Looks good to me. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #78 from Richard Mortimer --- (In reply to swatilodha27 from comment #77) > Richard, > > I tested your patch for adding referential integrity constraints in 5.0.0 v8 > DB and it seems to work fine for me. > >

[digikam] [Bug 322946] MYSQL : picture collection and database on a server can handle only one user

https://bugs.kde.org/show_bug.cgi?id=322946 --- Comment #9 from Richard Mortimer --- (In reply to swatilodha27 from comment #8) > Another thought, we could implement the internal locking methods. Since > there're already InnoDB tables present, we could use "row level

[digikam] [Bug 322946] MYSQL : picture collection and database on a server can handle only one user

https://bugs.kde.org/show_bug.cgi?id=322946 --- Comment #7 from Richard Mortimer --- (In reply to swatilodha27 from comment #6) > (In reply to Richard Mortimer from comment #5) ... snip ... > > > > - this also means that the referential integrity constraints/checks

[digikam] [Bug 322946] MYSQL : picture collection and database on a server can handle only one user

https://bugs.kde.org/show_bug.cgi?id=322946 --- Comment #5 from Richard Mortimer --- Before I answer the direct question let me make it clear that a "user" in this context is actually a "connection" to the shared MySQL database from a running digikam instance. It does

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #76 from Richard Mortimer --- Created attachment 99908 --> https://bugs.kde.org/attachment.cgi?id=99908=edit Add referential integrity constraints to a 5.0.0 v8 database The 5.0.0 initial release database

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #75 from Richard Mortimer --- Created attachment 99907 --> https://bugs.kde.org/attachment.cgi?id=99907=edit Raw commands to perform a full MySQL v7 to v8 update These can be used to test upgrades from v7 to v8

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #74 from Richard Mortimer --- Created attachment 99906 --> https://bugs.kde.org/attachment.cgi?id=99906=edit Helper to remove bad data prior to upgrade fromMySQL v7 to v8 Take care using this and always make a

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #73 from Richard Mortimer --- Created attachment 99905 --> https://bugs.kde.org/attachment.cgi?id=99905=edit helper SQL command to detect invalid data in v7 MySQL databases running these commands against a v7

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #72 from Richard Mortimer --- Created attachment 99904 --> https://bugs.kde.org/attachment.cgi?id=99904=edit Sample digikam v7 schema Here is my v7 based (digikam 4.x) MySQL schema. This may be useful for

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #71 from Richard Mortimer --- Created attachment 99903 --> https://bugs.kde.org/attachment.cgi?id=99903=edit Additional schema modifications from MySQL v7 to v8 Changes that need to be made for MySQL v7 to v8

[digikam] [Bug 322946] MYSQL : picture collection and database on a server can handle only one user

https://bugs.kde.org/show_bug.cgi?id=322946 Richard Mortimer changed: What|Removed |Added CC|

[digikam] [Bug 364131] SCAN : same picture with different file extensions : database scan only finds one variant of the file [patch]

https://bugs.kde.org/show_bug.cgi?id=364131 --- Comment #14 from Richard Mortimer --- Changing the collation is the correct thing to do. Regarding the patch the schema update is required but the v7 to v8 patch needs to perform an "alter table" command. The update has

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 --- Comment #20 from Richard Mortimer --- I like the look of Maik's patch. It does seem to be working in a portable way that does not rely on any magic database primary key values. A deleted AlbumRoot is easy to identify too.

[digikam] [Bug 363697] Album visible even after deletion [patch]

https://bugs.kde.org/show_bug.cgi?id=363697 Richard Mortimer changed: What|Removed |Added CC|

[digikam] [Bug 237878] SCHEMA : add foreign keys support

https://bugs.kde.org/show_bug.cgi?id=237878 --- Comment #12 from Richard Mortimer --- Gilles, I think we can say that we have the basic support there but there are still bugs to be worked out. I know Swati is working on those. Richard -- You are receiving this mail

[digikam] [Bug 283323] MYSQL : a new label "_Digikam_root_tag_" is created every time

https://bugs.kde.org/show_bug.cgi?id=283323 --- Comment #72 from Richard Mortimer --- I've tended to keep LONGTEXT and use a length on the index. That way a long tag name will not totally break things - but will likely cause unexpected behaviour. Try CREATE TABLE IF

[digikam] [Bug 283323] MYSQL : a new label "_Digikam_root_tag_" is created every time

https://bugs.kde.org/show_bug.cgi?id=283323 Richard Mortimer changed: What|Removed |Added CC|

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #69 from Richard Mortimer --- (In reply to swatilodha27 from comment #68) > Hello Richard. > > I guess then the only possible way is to reproduce every error reported by > the end user and try to generate it.

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #67 from Richard Mortimer --- Apart from testing and fixing issues I am aware of the following tasks that need completing for MySQL support. 1) Test and refine the "Experiment with TagsTree tables" patch to

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #66 from Richard Mortimer --- (In reply to swatilodha27 from comment #63) > Hello Richard. > > I'm Swati, currently working on digiKam MySQL database support project. I > read this open bug for MySQL Schema

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #65 from Richard Mortimer --- (In reply to Felix Leif Keppmann from comment #62) > > currently I face the issue of not being able to completely delete > directories. Directories are deleted on disk, but not

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #64 from Richard Mortimer --- Apologies. Life has caught up with me a little these past months. Things are still busy but here are a few thoughts... -- You are receiving this mail because: You are watching all

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #60 from Richard Mortimer --- Gilles, Many thanks for the information and the testing feedback. I have not had much time to look into this yet. A quick look at the schema does indicate that there is a missing

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #57 from Richard Mortimer --- (In reply to caulier.gilles from comment #56) > How to test quickly your new patch #95928 exactly ? General testing of the tags functionality with a MySQL database. I'm not 100% sure

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #55 from Richard Mortimer --- Created attachment 95928 --> https://bugs.kde.org/attachment.cgi?id=95928=edit Experiment with TagsTree tables. Build a TagsTree2 file that mimics the existing behaviour of the

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #39 from Richard Mortimer --- Gilles, 1) I did not yet get chance to rebase the other two patches to separate those from the face and thumbnail patches. I will do so within the next day. 2) I started to look at

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 --- Comment #36 from Richard Mortimer --- Created attachment 95824 --> https://bugs.kde.org/attachment.cgi?id=95824=edit Standalone MySQL face recognition settings to FaceSettings table Update face recognition MySQL

[digikam] [Bug 355831] MySQL Schema Improvements

https://bugs.kde.org/show_bug.cgi?id=355831 Richard Mortimer changed: What|Removed |Added Attachment #95755|0 |1 is