Removed dbal:import CLI command

[morozov]

Q	A
BC Break	yes
Fixed issues	#3237

The details are in #3237 (comment).

[Majkl578]

I'm going to be annoying and say that including only MySQL looks biased. :P Can we add alternatives that are also obvious?

Please use other database client applications for import,
e.g. `mysql < data.sql`, `psql < data.sql`, `cat data.sql | sqlite3 my.db` or equivalent.

[morozov]

I'll have to figure out the ways to import SQL dumps on all supported platforms, but in general, the proposal is legit. If you can add some more examples from the top of your head, please do.

BTW, isn't cat data.sql | sqlite3 my.db same as sqlite3 my.db < data.sql but with an extra process for cat?

[Majkl578]

I don't think we need all supported platforms, MySQL, MariaDB, PostgreSQL and SQLite is enough imho.

isn't cat data.sql | sqlite3 my.db same as sqlite3 my.db < data.sql

Likely yes. :)

$ sqlite3 <<<'select 123'
123

[morozov]

I don't think we need all supported platforms, MySQL, MariaDB, PostgreSQL and SQLite is enough imho.

Makes sense. I'll update the PR later.

$ sqlite3 <<<'select 123'
123

Speaking of which, isn't it a proper replacement for dbal:run-sql? Yes, it should work across the platforms but in the entire Tools namespace we have only two commands remaining: dbal:import, dbal:run-sql and dbal:reserved-words.

The latter, based on some recently discovered issues (e.g. #3152) may become obsolete in 3.0 since on the one hand, keywords cannot be fully supported in DBAL, on the other ORM should just quote everything. The notion of which names are reserved shouldn't be relevant for an app developer.