Hey, thanks for the work. I have very limited experience with Java, tried building the project but got some error. I know very little to conclude what went wrong. Here's the screenshot.

Would it be possible for you to release a jar for this?

Sorry if this is a bit out of topic.

Currently I want to merge two databases, an old one where messages are stored in messages table, and a new db where messages are stored in message table.

I read the new changes made by MrBarbie that makes merging between databases with the new, mid-2022 schema possible. But mine is on different schemas.

I tried restoring the old db into the latest whatsapp version, and creating a backup, then restoring again using the newly generated backup file. But the new backup file is still using old schema, and I'm at a loss here.

So back to the question, is there a way to convert the old db schema into the new one? I know that it is possible to generate a SQL query to do that but the whatsapp db structure is a bit overwhelming for me.

After my whatsapp databases are already using the latest/new schema, tried using the version updated by @MrBarbie.

But got some database consistency error, some are just as warning and stopped at RuntimeException for column message_vcard_jid.vcard_row_id. Reading from issue #2, @natario1 suggested to add the column into suggestion.

The thing is I don't know how to compile using gradle and kotlin. Want to try using sencodemaker's merger but it still not updated to account for the latest database schema.

The log is as below.

[*] Input databases:
        - input\msgstore.db
        - input\msgstore1.db
[*] Checking consistency of input\msgstore.db
        Column chat.jid_row_id is consistent! All 698 unique entries (out of 698) exist in the referenced table jid.
        Column chat.display_message_row_id is consistent! All 286 unique entries (out of 698) exist in the referenced table message.
        Column chat.last_message_row_id is consistent! All 286 unique entries (out of 698) exist in the referenced table message.
        Warning: Database input\msgstore.db is not consistent. Column chat.last_read_message_row_id references table message, where we expected to find a list of 235 entries, but only 234 were found.
Total count (source): 95991, total count (target): 698
Missing=[100846]
        Warning: Database input\msgstore.db is not consistent. Column chat.last_read_receipt_sent_message_row_id references table message, where we expected to find a list of 286 entries, but only 285 were found.
Total count (source): 95991, total count (target): 698
Missing=[100846]
        Column chat.last_important_message_row_id is consistent! All 2 unique entries (out of 698) exist in the referenced table message.
        Column chat.change_number_notified_message_row_id is consistent! All 3 unique entries (out of 698) exist in the referenced table message.
        Column chat.last_read_ephemeral_message_row_id is consistent! All 0 unique entries (out of 698) exist in the referenced table message.
        Column chat.last_message_reaction_row_id is consistent! All 9 unique entries (out of 698) exist in the referenced table message.
        Column chat.last_seen_message_reaction_row_id is consistent! All 9 unique entries (out of 698) exist in the referenced table message.
        Warning: Database input\msgstore.db is not consistent. Column chat.last_read_message_sort_id references table message, where we expected to find a list of 196 entries, but only 195 were found.
Total count (source): 95991, total count (target): 698
Missing=[100846]
        Column chat.display_message_sort_id is consistent! All 217 unique entries (out of 698) exist in the referenced table message.
        Column chat.last_message_sort_id is consistent! All 218 unique entries (out of 698) exist in the referenced table message.
        Warning: Database input\msgstore.db is not consistent. Column chat.last_read_receipt_sent_message_sort_id references table message, where we expected to find a list of 187 entries, but only 186 were found.
Total count (source): 95991, total count (target): 698
Missing=[100846]
        Warning: Database input\msgstore.db is not consistent. Column message.chat_row_id references table chat, where we expected to find a list of 457 entries, but only 456 were found.
Total count (source): 698, total count (target): 95991
Missing=[-1]
        Column message.sender_jid_row_id is consistent! All 702 unique entries (out of 95991) exist in the referenced table jid.
        Column message.sort_id is consistent! All 95990 unique entries (out of 95991) exist in the referenced table message.
        Column message_quoted.message_row_id is consistent! All 10651 unique entries (out of 10651) exist in the referenced table message.
        Column message_quoted.chat_row_id is consistent! All 118 unique entries (out of 10651) exist in the referenced table chat.
        Column message_quoted.parent_message_chat_row_id is consistent! All 152 unique entries (out of 10651) exist in the referenced table chat.
        Column message_quoted.sender_jid_row_id is consistent! All 303 unique entries (out of 10651) exist in the referenced table jid.
        Column message_vcard.message_row_id is consistent! All 67 unique entries (out of 71) exist in the referenced table message.
        Column message_vcard_jid.message_row_id is consistent! All 57 unique entries (out of 86) exist in the referenced table message.
Exception in thread "main" java.lang.IllegalStateException: Database input\msgstore.db is not consistent. Column message_vcard_jid.vcard_row_id references table message_vcard, where we expected to find a list of 61 entries, but only 60 were found.
Total count (source): 71, total count (target): 86
Missing=[-1]
        at dev.natario.ConsistencyKt.verifyConsistency(Consistency.kt:21)
        at dev.natario.ConsistencyKt.verifyConsistency$default(Consistency.kt:3)
        at dev.natario.MainKt.main(Main.kt:50)

Seems like in version 2.22.7.74 the schema changed a lot, most likely to this feature of being able to switch between iOS and Android more seamlessly.

This cool author blogpost has some info to get started with the changes, the TLDR is that the messages (plural) tables have been dropped and now they are called message and message_* and there are a few more.

https://thebinaryhick.blog/2022/06/09/new-msgstore-who-dis-a-look-at-an-updated-whatsapp-on-android/

Do you think you could find some time to update the tool? Ideally it would detect the version and would be able to merge both and migrate to the new schema for the output database.

I'm very interested in this so if you say that you won't be able to look at it anytime soon I might try to give it a chance but I'm new to Kotlin, only being able to run the project in IntelliJ took me an hour LOL.

Thanks in any case for this contribution!

Can you tell me a detail instruction on how to use the tool? Especially for windows user with little knowledge.

For example, how to arrange the msgstore.db; eg: I want to combine mgstore (6March) and mgstore (7March), how to do it? How about the naming scheme? naming it mgstore1.db for 7 March, and mgstore2.db for 6 March?

What command to make in cmd (windows) to combine it? How to define output file?

Hope you can answer this ASAP as I really on my end needs here :D Sorry for any bad English used.