Repository navigation
Zangi: read new ZZMESSAGE schema, tolerate missing ZUSER.ZSTATUS - #2255
Merged
Merged
Conversation
Newer Zangi builds moved message data out of the single ZZANGIMESSAGE table into a ZZMESSAGE table with per-message sender rows in ZZMESSAGEUSER and attachments in ZZMESSAGEMEDIA, so zangi_messages returned nothing (no such table: ZZANGIMESSAGE) and dropped every message on those extractions. Adds a second query for the new layout, selected per database from the table present, producing the same columns as the legacy query so the older layout keeps parsing. zangi_accounts read ZUSER.ZSTATUS unconditionally and failed (no such column) on a layout that lacks it; it now selects the ZUSER columns present and returns a missing one as NULL. Message type, direction (ZISRECEIVED) and the Cocoa timestamp mapping were field mapped from a private sample; no sample data recorded. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes a schema-drift regression in the Zangi Messenger artifact.
Newer Zangi builds moved message data out of the single ZZANGIMESSAGE table into a ZZMESSAGE table, with per-message sender rows in ZZMESSAGEUSER and attachments in ZZMESSAGEMEDIA. zangi_messages queried only ZZANGIMESSAGE, so on those databases it errored (no such table) and returned no messages. This adds a second query for the new layout, selected per database from the table present, and it returns the same columns as the legacy query so extractions from older app versions keep parsing.
zangi_accounts read ZUSER.ZSTATUS unconditionally and failed (no such column) on a layout that does not have it. It now selects the ZUSER columns that are present and returns a missing one as blank.
The new-layout message, sender, chat-name, media-path and Cocoa timestamp mapping and the ZISRECEIVED direction were field mapped from a private sample. Message type codes without a known mapping are reported as stored.