[Suggestion] Provide autocompletion for the DBAL query builder

[stof]

It would be great to provide autocompletion for the DBAL query builder (similar to what is done for the ORM query builder) based on the schema information known by PhpStorm if possible (it uses it to provide autocompletion in SQL queries already)

[stof]

This would technically not be specific to Symfony though. So you may provide it in a separate plugin for wider usage if it is not too much work about duplicating the infrastructure you created for your plugin (maybe you should extract this infrastructure in a dedicated package used as dependency by others btw, a kind of framework for PhpStorm plugins...)

[Haehnchen]

also ORM schema can be used to provide schema data, which would be an easy step to integrate but its not a common use case, i think. main target should be to reuse phpstorm database schema here. moreover is should not inside this plugin. a separate doctrine should be helpful. #295 #364

[King2500]

Can you exclude vendor/... or at least vendor/.../tests/... (fixtures) tables?
It gets a little annoying, with all these tables from external libraries, which are actually never used in my project.

Thanks.

[King2500]

Oh, and you can't use entity fields as insert/update fields, because they may not actually exist (like OneToMany or ManyToMany relations). ManyToOne fields mostly have _id appended depending on the Doctrine NamingStrategy.

Maybe better get all tables and columns from PhpStorm DataSources in project (Database panel), if that is possible. That way it's not necessarily bound to ORM entities.

[stof]

For the SQL query builder, reading the PhpStorm datasource is indeed the best way IMO if this is possible.