- 04 May, 2020 2 commits
-
-
Grégoire Paris authored
Upstream libs and tools have improvements that make them unnecessary.
-
Grégoire Paris authored
-
- 30 Mar, 2020 1 commit
-
-
Luís Cobucci authored
By either defining their types or renaming to match parent class (or interface).
-
- 29 Mar, 2020 1 commit
-
-
Luís Cobucci authored
-
- 16 Jan, 2020 1 commit
-
-
Sergey Linnik authored
also simplifies the code and now exactly matches postgresql search rules
-
- 07 Aug, 2019 1 commit
-
-
David Négrier authored
-
- 17 Mar, 2019 1 commit
-
-
Ahmed Abdou authored
-
- 29 Jan, 2019 1 commit
-
-
Sergei Morozov authored
-
- 22 Jan, 2019 1 commit
-
-
Sergei Morozov authored
-
- 24 Oct, 2018 1 commit
-
-
Sergei Morozov authored
-
- 16 Oct, 2018 2 commits
-
-
Ben Davies authored
-
Ben Davies authored
-
- 06 Oct, 2018 1 commit
-
-
Sergei Morozov authored
-
- 02 Oct, 2018 3 commits
-
-
Sergei Morozov authored
-
Sergei Morozov authored
-
Sergei Morozov authored
-
- 11 Jul, 2018 1 commit
-
-
Sergei Morozov authored
-
- 01 Jul, 2018 1 commit
-
-
Vladimir Reznichenko authored
-
- 15 May, 2018 1 commit
-
-
Alessandro Minoccheri authored
-
- 01 Apr, 2018 1 commit
-
-
Michael Moravec authored
-
- 29 Jan, 2018 2 commits
-
-
Michael Moravec authored
-
Gabriel Caruso authored
-
- 04 Jan, 2018 1 commit
-
-
Marco Pivetta authored
This reverts commit e3ab1276, reversing changes made to f988b0a6.
-
- 01 Jan, 2018 1 commit
-
-
Adrien Crivelli authored
-
- 26 Dec, 2017 1 commit
-
-
Simon Podlipsky authored
-
- 20 Nov, 2017 1 commit
-
-
Robin Appelman authored
- SERIAL and BIGSERIAL are not true types and can't be used in ALTER TABLE expressions - When changing between int and bigint auto increment fields the default should no be dropped to preserve the link between the column and the sequence.
-
- 18 Nov, 2017 1 commit
-
-
Christopher Davis authored
Serial fields already have a default value. By opting out of `notnull` serial fields will just set the next value in the sequence.
-
- 25 Jul, 2017 1 commit
-
-
Alessandro Minoccheri authored
-
- 19 Jul, 2017 1 commit
-
-
Luís Cobucci authored
-
- 09 Mar, 2017 1 commit
-
-
Chernyavtsev Ivan authored
-
- 15 Jul, 2016 1 commit
-
-
Steve Müller authored
Closes #2436
-
- 06 Jan, 2016 1 commit
-
-
Steve Müller authored
fixes #2270
-
- 01 May, 2015 1 commit
-
-
Steve Müller authored
-
- 25 Apr, 2015 1 commit
-
-
Benjamin Morel authored
-
- 11 Mar, 2015 1 commit
-
-
Wilt authored
Fixed inconsistent use of getSQLDeclaration method
-
- 31 Jan, 2015 1 commit
-
-
Roman Akhmadullin 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))"}``
-
- 21 Dec, 2014 1 commit
-
-
Claudio Zizza authored
-
- 16 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.
-