-
@wojtek actually the problem was in both the stored procedures, so the problem was partially fixed but not totally fixed, as you find out
-
Yes, there is also #1539 that uses
LAST_INSERT_ID
but while it causes performance issues it's different from this one. -
@wojtek I've applied discussed changes and pushed them to
offlinestorage-schema
branch for a review. -
@andrzej.wojcik Why index creation is missing from mysql schema? It was in
src/main/database/mysql-server-8.5.0.sql
and looks like the intention was to move it tosrc/main/database/mysql-server-8.5.0-schema.sql
but, I guess, was not saved/stashed/committed? (judging by the changes in other schemas)
Type |
Task
|
Priority |
Normal
|
Assignee | |
Version |
tigase-server-8.2.0, tigase-server-8.5.0
|
Spent time |
0
|
Iterations
-
tigase-server-8.5.0 Open
-
tigase-server-8.2.0 Closed
Issue Votes (0)
In
Tig_OfflineMessages_DeleteMessage()
we have a callselect row_count() as deleted_rows;
(https://github.com/tigase/tigase-server/blob/05fa90bfa40ad4b253819b4be7b897fd76b7c8b2/src/main/database/mysql-issue #8.0.0-sp.sql#L185-L185)but in
tigase.server.amp.db.JDBCMsgRepository#deleteMessage
(https://github.com/tigase/tigase-server/blob/05fa90bfa40ad4b253819b4be7b897fd76b7c8b2/src/main/java/tigase/server/amp/db/JDBCMsgRepository.java#L483-L483) we don't use it?We should change the SP to:
to avoid performance penalty.