[GH-ISSUE #3] source db can use sql files? #2

New issue

Closed

opened 2026-02-25 21:33:00 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 21:33:00 +03:00

Owner

Originally created by @dwdcth on GitHub (Apr 12, 2016).
Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/3

Thanks for your great work!
Our production dbs are only allowed to access in local netwrok.
We dump developing dbs to sql files and restore them to production dbs.
If source db can use sql files?

Originally created by @dwdcth on GitHub (Apr 12, 2016). Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/3 Thanks for your great work! Our production dbs are only allowed to access in local netwrok. We dump developing dbs to sql files and restore them to production dbs. If source db can use sql files?

kerem closed this issue

2026-02-25 21:33:00 +03:00

kerem commented

2026-02-25 21:33:00 +03:00

Author

Owner

@jasdeepkhalsa commented on GitHub (Apr 15, 2016):

Apologies for the delayed reply!

For database access, internally we are using Laravel's database connectivity module called illuminate/database which only supports MySQL, Postgres, SQLite, and SQL Server. As a result you would not be able to use DBDiff without the SQL file being inside a database.

Also, currently we're only supporting MySQL properly in order to see if this tool is really being demanded by the community first, and iron out any issues.

As a result, for your purposes, you may want to try to get your SQL file added into a temporary MySQL database on your laptop / machine in order to produce your migrations. You can always destroy that temporary database later :)

@jasdeepkhalsa commented on GitHub (Apr 15, 2016): Apologies for the delayed reply! For database access, internally we are using [Laravel](https://laravel.com)'s database connectivity module called `illuminate/database` which only supports `MySQL, Postgres, SQLite, and SQL Server`. As a result you would not be able to use DBDiff without the SQL file being inside a database. Also, currently we're only supporting MySQL properly in order to see if this tool is really being demanded by the community first, and iron out any issues. As a result, for your purposes, you may want to try to get your SQL file added into a temporary MySQL database on your laptop / machine in order to produce your migrations. You can always destroy that temporary database later :)

kerem commented

2026-02-25 21:33:00 +03:00

Author

Owner

@dwdcth commented on GitHub (Apr 16, 2016):

OK, a a temporary database maybe a solution.Thank you !

@dwdcth commented on GitHub (Apr 16, 2016): OK, a a temporary database maybe a solution.Thank you !

kerem referenced this issue

2026-02-25 21:33:03 +03:00

[GH-ISSUE #32] Fail to find table #20

kerem referenced this issue

2026-02-25 21:33:10 +03:00