You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 9, 2023. It is now read-only.
snaplet snapshot capture had an issue that was causing us to load all of the table’s rows in memory.
If you have large tables (e.g. a table with many rows, or a table with very large values for each row), this might have prevented you from capturing snapshots (either locally with snaplet snapshot capture, or using app.snaplet.dev.
Other bug fixes
snaplet snapshot capture or snaplet snapshot restore fail with errors, we’re now correctly exiting with a non-zero exit code
snaplet seed now handles generating data for significantly more postgres column types than it previously would
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
snaplet snapshot capture
had an issue that was causing us to load all of the table’s rows in memory.If you have large tables (e.g. a table with many rows, or a table with very large values for each row), this might have prevented you from capturing snapshots (either locally with
snaplet snapshot capture
, or using app.snaplet.dev.Other bug fixes
snaplet snapshot capture
orsnaplet snapshot restore
fail with errors, we’re now correctly exiting with a non-zero exit codesnaplet seed
now handles generating data for significantly more postgres column types than it previously wouldBeta Was this translation helpful? Give feedback.
All reactions