Is your feature request related to a problem? Please describe.
Currently, we can seed initial data from only .sql files, which is a problem for big databases to start from. For people working with db-first mentality this is a problem. For example, i store my seed files in gzipped sql.gz files, so that they don't take much space in the disk or repository if commited.
Describe the solution you'd like
Support configuring .sql.gz files, and uncompressing them before seeding into db. It should auto-detect from the extension.
Describe alternatives you've considered
Currently, i am not using automatic seeding, but i am restoring my initial db manually each time i reset local db.
Is your feature request related to a problem? Please describe.
Currently, we can seed initial data from only .sql files, which is a problem for big databases to start from. For people working with db-first mentality this is a problem. For example, i store my seed files in gzipped sql.gz files, so that they don't take much space in the disk or repository if commited.
Describe the solution you'd like
Support configuring .sql.gz files, and uncompressing them before seeding into db. It should auto-detect from the extension.
Describe alternatives you've considered
Currently, i am not using automatic seeding, but i am restoring my initial db manually each time i reset local db.