Archive message stores two copies of same kind of data (#12)
Won't Fix
Khaleel Shaik opened 10 years ago

Hi,

For every conversation between the users the archive component saves two records. Only difference is that the FROM USER and TO USER will be replaced.

Could you please help us why we need two records for same message? If have to save single message is there any configuration we can do on the system?

Regards

Khaleel

Andrzej Wójcik (Tigase) commented 10 years ago

Message is stored in two records as each user should have separate copy of chat history so user could manage it's own copy of chat history. Right now management is not implemented yet but database layout is prepared to support this feature.

Khaleel Shaik commented 10 years ago

Hi,

Thanks for your rocket speed response. I appreciate a lot.

My requirement is there will be no deletion of history at any point of time. So If I have to maintain single copy for the better database management, Can I have any parameter configured or any other inputs that need code changes to implement this without effecting any other functionality?

Thanks in advance

Khaleel

Andrzej Wójcik (Tigase) commented 10 years ago

Right now there is no such configuration parameter.

To add such a parameter would need to rewrite database access layer (mostly preparation of alternative SQL queries) which would handle alternative database schema.

Artur Hefczyc commented 10 years ago

Khaleel, while I agree that the way message archive is currently store could be optimized, it is not as simple or trivial as it seems. There are a few things which need to be taken into consideration:

  1. As Andrzej pointed out, each user can manage own archive independently, can remove messages at any time

  2. The archive is supposed to work also correctly if one of the user is on a different server

I am not saying that it impossible exceptionally difficult but it just needs a considerable amount of work to make sure it works correctly. So at the moment it is not possible to have a single copy only.

If you are interested in sponsoring of the feature implementation, we would can move this database optimization on top of our development schedule.

issue 1 of 1
Type
Question
Priority
Blocker
Assignee
RedmineID
2294
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/tigase-message-archiving#12
Please wait...
Page is in error, reload to recover