- 15 Jul, 2016 1 commit
-
-
Steve Müller authored
Closes #2436
-
- 12 Jan, 2016 1 commit
-
-
Steve Müller authored
fixes #2270
-
- 05 Sep, 2015 1 commit
-
-
Steve Müller authored
-
- 03 Jan, 2015 1 commit
-
-
Adrien Crivelli authored
Because PostgreSQL will return the expression with a lot of parentheses we cannot TRIM() them easily. It is easier and more correct to adapt to what PostgreSQL returns. That means the declaration of partial indexes must be updated as follow: Before: ``options={"where": "other_id IS NULL"}`` After: ``options={"where": "(other_id IS NULL)"}`` And fore more complex conditions, that would be: ``options={"where": "(((id IS NOT NULL) AND (other_id IS NULL)) AND (name IS NULL))"}``
-
- 26 Dec, 2014 1 commit
-
-
Claudio Zizza authored
-
- 24 Dec, 2014 1 commit
-
-
Jeroen Thora authored
-
- 10 Nov, 2014 1 commit
-
-
Jan Sorgalla authored
This excludes views registered by PostGIS 2.x like geography_columns, geometry_columns, raster_columns and raster_overviews. The table_name != 'geometry_columns' is kept for PostGIS 1.5 compatibility. The type changed to VIEW in PostGIS 2.0.
-
- 05 Nov, 2014 13 commits
-
-
Steve Müller authored
-
Steve Müller authored
-
x42p authored
some format changes to trigger travis-cl once more again
-
x42p authored
I take the guess an use the information_schema. It makes it more clear and simple
-
x42p authored
correct table identifier
-
x42p authored
missing table identifier added
-
x42p authored
If the database have different schemes, with objects, that the actual logged in user has no rights, the existing statements will collect all objects (sequences and tables) and try to read them in later steps. This will throws exceptions. The reason for that is the fact, that both procedures getListSequencesList() and getListTablesSQL() will receive all known database objects from postgres catalogs. But the actual logged-in user, maby has no read permissions to object inside other scheme-owner. The additional parts inside both sql-statements will reduce the result to only objects that the user are able to see.
-
Tiago Brito authored
-
Tiago Brito authored
-
Tiago Brito authored
Add new line after an IF statement to be consistent with the coding standard
-
Tiago Brito authored
-
Tiago Brito authored
-
Steve Müller authored
-
- 31 Oct, 2014 1 commit
-
-
Steve Müller authored
-
- 23 Oct, 2014 6 commits
-
-
Steve Müller authored
-
x42p authored
some format changes to trigger travis-cl once more again
-
x42p authored
I take the guess an use the information_schema. It makes it more clear and simple
-
x42p authored
correct table identifier
-
x42p authored
missing table identifier added
-
x42p authored
If the database have different schemes, with objects, that the actual logged in user has no rights, the existing statements will collect all objects (sequences and tables) and try to read them in later steps. This will throws exceptions. The reason for that is the fact, that both procedures getListSequencesList() and getListTablesSQL() will receive all known database objects from postgres catalogs. But the actual logged-in user, maby has no read permissions to object inside other scheme-owner. The additional parts inside both sql-statements will reduce the result to only objects that the user are able to see.
-
- 21 Oct, 2014 1 commit
-
-
Steve Müller authored
-
- 20 Oct, 2014 1 commit
-
-
Steve Müller authored
-
- 17 Oct, 2014 1 commit
-
-
Steve Müller authored
-
- 21 Aug, 2014 1 commit
-
-
Jérôme Brissonnet authored
-
- 18 Aug, 2014 2 commits
-
-
Steve Müller authored
-
Steve Müller authored
-
- 29 Jul, 2014 2 commits
-
-
Tiago Brito authored
-
Tiago Brito authored
-
- 24 Jul, 2014 2 commits
-
-
jeroendedauw authored
-
jeroendedauw authored
-
- 22 Jul, 2014 3 commits
-
-
Tiago Brito authored
Add new line after an IF statement to be consistent with the coding standard
-
Adrien Crivelli authored
-
Adrien Crivelli authored
Support for Partial Indexes was available in Doctrine 1 following http://www.doctrine-project.org/jira/browse/DC-82. This commit reintroduce support for Doctrine 2. We use the same syntax with an optionnal "where" attribute for Index and UniqueConstraint.
-