[DBAL-147] PostgreSqlSchemaManager fails to set foreign key onDelete/Update option properly if table has 'SET NULL' or 'SET DEFAULT' foreign key constraints Created: 15/Aug/11 Updated: 27/Aug/11 Resolved: 27/Aug/11
|Reporter:||Payam Hekmat||Assignee:||Benjamin Eberlei|
This table structure:
will cause the listTableForeignKeys to produce incorrect results for the onDelete/Update constraints (the 'DEFAULT' or 'NULL' in 'SET DEFAULT' or 'SET NULL' respectively gets cut off).
This looks to be fixed in the main branch.
|Comment by Kenny Millington [ 26/Aug/11 ]|
Seems to be fixed in:-
Would definitely be nice to have that ported to the 2.1.x branch.
|Comment by Benjamin Eberlei [ 27/Aug/11 ]|
Fixed and merged for 2.1.2