Fix: Large Database Export Memory Overflow (#59) #486
+402
−348
Conversation
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.
Exporting large tables currently causes a browser crash/hang because the entire result set is loaded into memory as a single array and joined into a massive string.
Changes
Modified exportTableData in src/lib/export-helper.ts to use a while loop with LIMIT and OFFSET.
Data is now fetched and processed in batches of 2,000 rows.
Verified driver compatibility using the internal escapeId method.
Impact
This resolves the memory exhaustion issue for large database exports (Issue #59), allowing for stable exports regardless of table size.