In some cases the Comparator class returns multiple drops for the same foreign key.
Specifically, in case you have two tables, A & B, with A having a foreign key FK
referencing B, if you drop table B, the resulting diff shows this FK twice,
once on the diff->orphanedForeignKeys array as we're deleting B, and another on
the diff->changedTables array as table A is also being modified. As a result of this you
get the DROP FOREIGN KEY instruction twice in the final SQL.

Based on whether we are on 32 or 64 bit platform, postgres will return a string or an int for the expected php type of a bigint that is > 32 bits.

Use dropAndCreateDatabase schema manager function in test initialization instead of individual versions of each.

Changed 'implements' by 'extends' because AbstractSchemaSynchronizer is a class not an interface (and Eclipse PDT shows a warning that say that "The type SQLAzureFederationsSynchronizer must implement the inherited method processSqlSafely, processSql" but those methods are already implemented on AbstractSchemaSynchronizer).

Unsigned column properties were never set. In consequence all migrations diff were trying to change the column definition when it was already changed.

previous changes in bindparam function

bindParam function expects length parameter for oci_bind_by_name oci8