Reintroduce support for multi-db setups

[benpoulson]

This snipet was lost in the 2.12.x => 2.13.x change. Needs to be reintroduced to allow those who use fully qualified db+table names. (Eg, database.table)

Summary

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Misc. change (internal, infrastructure, maintenance, etc.)

Checklist

• Existing tests have been adapted and/or new tests have been added
• Add a CHANGELOG.md entry
• Update the README.md
• Code style has been fixed via composer fix-style

[mfn]

This snipet was lost in the 2.12.x => 2.13.x change. Needs to be reintroduced to allow those who use fully qualified db+table names. (Eg, database.table)

Technically it wasn't "lost". The change is due to https://github.com/barryvdh/laravel-ide-helper/pull/1349/files

If we're going forward with this PR, we're now keeping a very mixed state here and I'm not sure anyone understands the outcome.

Original code:

        $database = null;
        if (strpos($table, '.')) {
            [$database, $table] = explode('.', $table);
        }

PR #1349:

        $database = $model->getConnection()->getName();
…
        $columns = $schema->listTableColumns($table, $database);

This PR:

        $database = $model->getConnection()->getName();
…
        if (strpos($table, '.')) {
            [$database, $table] = explode('.', $table);
        }

I.e. is the $database = $model->getConnection()->getName(); really needed when we bring back the explode?

I think my cautious side suggests we revert PR #1349 rather in its entirety.

WDYT?

[makroxyz]

Any news about this PR?

[technikman]

I had the same problem and this solution brings back the old function

[barryvdh]

I'm not really sure. @mikebouwmans what do you think? Does this work for you?

[makroxyz]

Any news about this PR?
I'm still locked to v2.12.3...

[ThomasSfflx]

Me too...
Any chance to have news on this topic ?

[jameshulse]

Closes #1487