https://bugs.kde.org/show_bug.cgi?id=355831
Richard Mortimer changed:
What|Removed |Added
Attachment #95755|0 |1
is obsolete|
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&action=edit
Standalone MySQL face recognition settings to FaceSettings table
Update face recognition MySQL support.
Use FaceSettings
https://bugs.kde.org/show_bug.cgi?id=355831
Richard Mortimer changed:
What|Removed |Added
Attachment #95823|0 |1
is obsolete|
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 the Tags and Albums icon cod
https://bugs.kde.org/show_bug.cgi?id=322946
Richard Mortimer changed:
What|Removed |Added
CC||richm+...@oldelvet.org.uk
--- Comment #3 fro
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&action=edit
Additional schema modifications from MySQL v7 to v8
Changes that need to be made for MySQL v7 to v8 transition in addition
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&action=edit
Sample digikam v7 schema
Here is my v7 based (digikam 4.x) MySQL schema. This may be useful for testing
the upgrade from v
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&action=edit
helper SQL command to detect invalid data in v7 MySQL databases
running these commands against a v7 database will list any
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&action=edit
Helper to remove bad data prior to upgrade fromMySQL v7 to v8
Take care using this and always make a backup of your datab
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&action=edit
Raw commands to perform a full MySQL v7 to v8 update
These can be used to test upgrades from v7 to v8 standalone from digi
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&action=edit
Add referential integrity constraints to a 5.0.0 v8 database
The 5.0.0 initial release database upgrade does not add refer
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 not matter whether that conn
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 are
> > vital to the correct o
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 locking".
> This would allow
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.
>
> Thanks.
Thanks for testing.
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.
https://bugs.kde.org/show_bug.cgi?id=365354
Richard Mortimer changed:
What|Removed |Added
CC||richm+...@oldelvet.org.uk
--- Comment #7 fro
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 equivalent "fix".
Has anyone worked
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.
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 have been resolved.
--
You a
https://bugs.kde.org/show_bug.cgi?id=325655
Richard Mortimer changed:
What|Removed |Added
CC||richm+...@oldelvet.org.uk
--- Comment #4 fro
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
database types to see if th
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 issue with Swati via email today
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 because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=363697
Richard Mortimer changed:
What|Removed |Added
CC||richm+...@oldelvet.org.uk
--- Comment #14 fr
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.
A few comments on the patc
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 to assume that the v7
schema
https://bugs.kde.org/show_bug.cgi?id=283323
Richard Mortimer changed:
What|Removed |Added
CC||richm+...@oldelvet.org.uk
--- Comment #69 fr
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 NOT EXISTS Tags
https://bugs.kde.org/show_bug.cgi?id=355831
--- Comment #42 from Richard Mortimer ---
Created attachment 95860
--> https://bugs.kde.org/attachment.cgi?id=95860&action=edit
Store empty icon (image 0) as a NULL value
Tested on both SQLite and MySQL databases. Album and tag icons can be set and
c
https://bugs.kde.org/show_bug.cgi?id=355831
Richard Mortimer changed:
What|Removed |Added
Attachment #95731|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=355831
--- Comment #47 from Richard Mortimer ---
(In reply to caulier.gilles from comment #46)
> Richard,
>
> Did you plan to specific ImnoDb database type with Mysql for Core database
> creation action, as with Thumbs and Face databases ?
Yes. That seems to
https://bugs.kde.org/show_bug.cgi?id=355831
--- Comment #48 from Richard Mortimer ---
Created attachment 95865
--> https://bugs.kde.org/attachment.cgi?id=95865&action=edit
MySQL database permissions/setup guidance streamlining.
Make it clear that the password is specific to the account/hostnam
https://bugs.kde.org/show_bug.cgi?id=355831
--- Comment #49 from Richard Mortimer ---
Created attachment 95866
--> https://bugs.kde.org/attachment.cgi?id=95866&action=edit
Specify InnoDB engine on setup for coredb tables.
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=355831
--- Comment #50 from Richard Mortimer ---
Created attachment 95867
--> https://bugs.kde.org/attachment.cgi?id=95867&action=edit
Do not migrate "zero" icon values for Albums and Tags
MySQL referential integrity does not allow to refer to a non-existan
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&action=edit
Experiment with TagsTree tables.
Build a TagsTree2 file that mimics the existing behaviour
of the MySQL Tags table and use
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 how to test it all but a lot
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 UNIQUE clause
in the Tags tab
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 bug changes.
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 deleted from the
> database, i.e.
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 improvements and thought of a pla
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 ensure that
it maintains the tags
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.
Some errors may be obvious by
43 matches
Mail list logo
