Updated tables to October2022 Schema #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Initial work in progress update for october schema, does not build currently
Updated ignoreConsistencyChecks and switched order of `chat` and `messsage` tables. Also fixed some formatting inconsistencies
Change is intended to get around behaviour of the code when mapping and offsetting referenced ids. Intended to go with Main.kt Circular "capable" version 2.2 Because Mapping is done before processing the tables which identifies uniques, the values are offset too far because those entries duplicated unique indexes are still there and hence counted for offset. By processing `chat` first, the chance of a potentially in accurate mapping is lower as `message` should not contain entries which have the unique indexes clashing. The only scenario this will happen is if there are duplicated msgs. Whereas with `chat` it is gauranteed to contain a clash if you have continuously interacted with at least 1 contact and had new ones as well. Effect: In the previous order chat_row_ids will be in accurate if there were lines are skipped due to unique indexes set for `chat` table, where the likelihood is much higher than `message` table.
Updated main.kt to break up the processing of table to the following order: >process `jid` >map `message` >process all non `jid` tables starting with `chat` The 3 main table have to be in listed in the specific order or `jid` > `chat` > `message` in Schema.kt
Increased the amount of offset by1 to avoid overlap due to `message` table behaviour listing 0 as jid when it is one-to-one chats and for messages from self. Where before all those jid will overlap with the last jid in the first database. As of now it doesnt affect the display of those messages as all the other infromation makes it display correctly, but would it break in the future? who knows. This change makes it easier for the user to search for those jids that should be 0 be searching for the id that will be reported as missing in the output consistency check. They can then fix it if they like. The user needs to change the `sort_id` for the first line in `message` table to 1 from 0, otherwise you will not get the full output consistency check as it will fail on this column.
Allow full output consistency check to be completed even with offset increased by 1. You should expect to see 1 entry missing that will be +1 of the first table's jid entries.
Added the following tables: `message_location`, `message_mentions`, `message_quoted_location`, `message_quoted_media`, `message_quoted_mentions`, `message_quoted_text`, `message_quoted_vcard`, `message_ftsv2_docsize`, `message_ftsv2_content`, `message_view_once_media`, `community_chat`, `call_log`, `call_log_participant_v2`,
Fixed missing `,` for the additional timestamp parameter for some tables that were added in last commit
Removed selfRef that doesnt exist. Also fix some formatting with indents
Why the change to -1 instead of 0????
|
@natario1 This should now included all fixes discussed in #5 to have the tool working again. There is one unresolved inconsequential problem described in 26bf3f0. The branch is intended to fix it with some manual intervention outside of the tool as I have no capability to update this tool to deal with it. |
|
I shall leave the version revision to you |
|
Apologies for the mess of the last few commits since the last msg. Did an oopsie and had to fix it which also went a bit weird |
Added info on the schema version name by WhatsApp. This info can be found by browsing the `props` table with the value `msgtore_db_schema_version` in the `key` column
All current tables have appropriate timestamps defined
Added ignoreConsistencyChecks so it doesnt fail on `-1` id reported in a user's database. My own had reference which was missing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated all the present tables to the October2022 Schema.