https://bugs.kde.org/show_bug.cgi?id=322946
caulier.gil...@gmail.com changed:
What|Removed |Added
Severity|normal |wishlist
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=322946
Maik Qualmann changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=322946
--- Comment #12 from Joerg Beschorner ---
sorry but I didn't continue to explore this issue.
In case I try it again I will report the result.
Regards Joerg
Am 06.11.22 um 10:25 schrieb Justin Zobel:
> https://bugs.kde.org/show_bug.cgi?id=322946
>
> Ju
https://bugs.kde.org/show_bug.cgi?id=322946
Justin Zobel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=322946
Thomas Debesse changed:
What|Removed |Added
CC||d...@illwieckz.net
--- Comment #10 from Thomas
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=322946
--- Comment #8 from swatilodh...@gmail.com ---
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 multiple write access, making it suitable fo
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 #6 from swatilodh...@gmail.com ---
(In reply to Richard Mortimer from comment #5)
> 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
> runn
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 #4 from caulier.gil...@gmail.com ---
Richard,
Seriously, Mysql do not have a mechanism to lock database to prevent
concurrency access to the data on the same time ? How it's possible (:=))). Or
i miss understand something in database server
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=322946
swatilodh...@gmail.com changed:
What|Removed |Added
CC||swatilodh...@gmail.com
--- Comment #2 f
https://bugs.kde.org/show_bug.cgi?id=322946
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Database-Mysql |Database-Multiusers
--
You are recei
14 matches
Mail list logo
