- 05 Nov, 2014 40 commits
-
-
Steve Müller authored
-
Steve Müller authored
-
Steve Müller authored
-
Steve Müller authored
-
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.
-
Steve Müller authored
-
Tobias Schultze authored
-
Tiago Brito authored
-
Tiago Brito authored
-
Tiago Brito authored
-
Tiago Brito authored
Add unit test to check boolean conversion with and without PDO boolean type
-
Tiago Brito authored
Add functional test to check null conversion with boolean type. This test required NULL to be allowed in the table column.
-
Tiago Brito authored
Add new line after an IF statement to be consistent with the coding standard
-
Tiago Brito authored
-
Tiago Brito authored
-
Tiago Brito authored
-
Thomas Müller authored
-
Steve Müller authored
-
Martin Hasoň authored
-
marius.klocke authored
-
marius.klocke authored
-
Marco Pivetta authored
-
malukenho authored
-
malukenho authored
-
malukenho authored
-
Christophe Coevoet authored
The inner connection should be unreferenced, but the property should not be removed from the object
-
Steve Müller authored
-
Francisco Facioni authored
As seen here => http://technet.microsoft.com/en-us/library/cc626307(v=sql.105).aspx
-
Pavel Horal authored
TimeType resets date fields (i.e. unused DateTime object fields) to UNIX epoch (1970-01-01). This makes TIME field mapping stabe (i.e. same time will be always mapped to the same DateTime fields). See DDC-179 (similar issue with DateType). Fixes DBAL-993.
-
Marco Pivetta authored
-
Steve Müller authored
-
Steve Müller authored
-
Steve Müller authored
-
Marco Pivetta authored
-