Table foreign keys load two times as arrays and as objects about db

[Tigrov]

Yes, it looks like this. And use ForeignKeyConstraint[] instead of associative arrays.

[Tigrov]

Perhaps the solution could be use AbstractSchema::getTableMetadata() into Schema::findConstraints() of each DB specific package?

Or AbstractSchema::getTableForeignKeys()

[vjik]

Perhaps the solution could be use AbstractSchema::getTableMetadata() into Schema::findConstraints() of each DB specific package?

[vjik]

@darkdef @terabytesoftw What do you think?

[Tigrov]

Suggestion to use one way to get foreign keys Schema::getTableForeignKeys() and do not store them in TableSchemaInterface as for indexes