orisintel / laravel-migration-snapshot Goto Github PK

Currently dumping data with schema may produce a data.sql file whose inserts vary only by the dates/times of when the migrations created the data. It would be nice to have an --epoch= option when dumping with data to replace those dumped dates-times with the provided value.

Possible solutions could be to manipulate the data in memory during the dump/export or temporarily update the data in a DB transaction beforehand. If there is no maintainable solution then it may be best to simply document the limitation in the README.md.

Hi,

I think there's a typo in README.md:

php artisan vendor:publish --provider="\OrisIntel\MigrationSnapshot\ServiceProvider"

produces error (I'm on Windows):

Unable to locate publishable resources.

It works if changed to:

php artisan vendor:publish --provider="OrisIntel\MigrationSnapshot\ServiceProvider"

(mind the first backslash)

Write code or best-practice documentation to maintain consistent batch numbers in the migration rows dumped into schema.sql. At present one may get all zeros after migrate:fresh yet an incremental sequence if dumped from a stepped or progressively applied series of migrations.

Ideally the schema.sql contents would be consistent regardless of how DB being dumped was migrated, or the DBMS server version used with migrate:dump.

Filtering AUTO_INCREMENT= values currently relies on Bash-specific set -o pipefail, &&, shell piping, and sed. Instead do the filtering in PHP code for maximum compatibility.

This may also be a good time reconsider using proc_open or temporary file(s) to capture Stdout and Stderr within PHP to filter password-insecure warnings and colorize output. Then console output would look more like that produced by $this->info() and $this->error() within Artisan commands.

Hi,

Would it be possible to add php 8 support?

Thanks for this awesome package!