- 09 Jan, 2016 1 commit
-
-
Steve Müller authored
-
- 21 May, 2015 1 commit
-
-
Martin Poirier Théorêt authored
According to the comment // deleting duplicated foreign keys present on both on the orphanedForeignKey // and the removedForeignKeys from changedTables A check must be had on the $removedForeignKey so it does point on the removed table. Currently it does unset all keys removal even the one pointing on other table.
-
- 03 Jan, 2015 1 commit
-
-
Steve Müller authored
-
- 17 Oct, 2014 1 commit
-
-
Steve Müller authored
-
- 10 Sep, 2014 1 commit
-
-
Steve Müller authored
-
- 18 Aug, 2014 2 commits
-
-
Steve Müller authored
-
Marco Pivetta authored
Updating a schema should introduce also schema creation statements in the generated SQL
-
- 10 Feb, 2014 2 commits
-
-
Martin Hasoň authored
-
Martin Hasoň authored
-
- 29 Dec, 2013 1 commit
-
-
Steve Müller authored
-
- 22 Dec, 2013 2 commits
-
-
Steve Müller authored
-
Steve Müller authored
-
- 21 Dec, 2013 1 commit
-
-
Steve Müller authored
-
- 20 Dec, 2013 1 commit
-
-
Artur Bodera authored
-
- 19 Dec, 2013 1 commit
-
-
Kirill chEbba Chebunin authored
-
- 24 Nov, 2013 1 commit
-
-
Steve Müller authored
-
- 21 Jun, 2013 1 commit
-
-
Benjamin Morel authored
- Fixed docblocks - Removed return statements on void methods - Cleaned up unused private / local variables - Fixed license issues - Removed SVN leftovers - Fixed doctrine-project.org links - Added line breaks before return statements
-
- 14 Apr, 2013 1 commit
-
-
Benjamin Eberlei authored
-
- 24 Nov, 2012 1 commit
-
-
Alessandro Tagliapietra authored
-
- 17 Nov, 2012 1 commit
-
-
Martin Hasoň authored
-
- 09 Oct, 2012 1 commit
-
-
Lee Davis authored
-
- 05 Oct, 2012 1 commit
-
-
Lee Davis authored
-
- 04 Oct, 2012 5 commits
-
-
Sergi de Pablos authored
-
Sergi de Pablos authored
-
Lee Davis authored
-
Lee Davis authored
-
Sergi de Pablos authored
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.
-
- 16 Jul, 2012 1 commit
-
-
Pascal Borreli authored
-
- 08 Jul, 2012 1 commit
-
-
Benjamin Eberlei authored
[DDC-1657] Prevent autoincrement sequences from creating DROP SEQUENCE statements because of old/new schema missmatch.
-
- 25 May, 2012 1 commit
-
-
Benjamin Eberlei authored
-
- 24 Mar, 2012 3 commits
-
-
Benjamin Eberlei authored
-
Benjamin Eberlei authored
-
Benjamin Eberlei authored
-
- 21 Jan, 2012 1 commit
-
-
Benjamin Eberlei authored
-
- 19 Jan, 2012 1 commit
-
-
Benjamin Eberlei authored
[DBAL-204] Sane refactoring of the previous idea. Removed a bunch of code again and implemented proper schema namespacing. Also got the wording right (hopefully) and fixed the algorithms.
-
- 18 Jan, 2012 1 commit
-
-
Benjamin Eberlei authored
-
- 19 Dec, 2011 1 commit
-
-
Benjamin Eberlei authored
-
- 14 Dec, 2011 1 commit
-
-
jsor authored
-
- 13 Dec, 2011 1 commit
-
-
jsor authored
-
- 31 Jul, 2011 1 commit
-
-
Benjamin Eberlei authored
-