[Digikam-devel] [Bug 271924] digikam fail to create/update mysql database on startup [PATCH]

[Francesco Riosa]

https://bugs.kde.org/show_bug.cgi?id=271924





--- Comment #4 from Francesco Riosa <francesco pnpitalia it>  2011-04-29 13:34:30 ---
(In reply to comment #3)
> Francesco,
> 
> What about these entries ? That can be fixed with your patch ?
> 
> https://bugs.kde.org/show_bug.cgi?id=258409
not this one, seem related to this error message:
QSqlQuery::seek: cannot seek backwards in a forward only query
Dunno what exactly can be, maybe a server side cursor where a client side one
should have been used


> https://bugs.kde.org/show_bug.cgi?id=257183
yes if the triggers for the relevant table are wrong and not deleted and
re-created then this bug could be fixed

> https://bugs.kde.org/show_bug.cgi?id=233763
IMHO when when one of ip,server,port change in the dialog the database should
be checked (including DBVersion in digikam.settings). If not existant it should
be created, or if current db is valid a warning telling to use the database
migration tool.


> https://bugs.kde.org/show_bug.cgi?id=267733
"The Internal MySQL box in option menu is blank. "
In my case it was populated with correct values both in 1.9.0 and 2.0
would tell the user to re-test and close if not confirmed

> https://bugs.kde.org/show_bug.cgi?id=262231
mmh, may be best to disable triggers during mass migration, then do a cleanup
following the same rules i.e. 
delete a.* from a LEFT JOIN b on a.id = b.id where ISNULL(b.id)
then reenable them
mysqldump tool may be inspirational here

> https://bugs.kde.org/show_bug.cgi?id=233770
yes should be fixed

P.S. I do grok enough of mysql sql language and behaviour, and very pleased to
use digikam, feel free to contact me whenever you want also by private email

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.