1. 20 Aug, 2014 2 commits
  2. 04 Aug, 2014 2 commits
  3. 29 Jul, 2014 3 commits
  4. 27 Jul, 2014 2 commits
  5. 23 Jul, 2014 2 commits
  6. 22 Jul, 2014 1 commit
  7. 08 Feb, 2014 5 commits
  8. 05 Jan, 2014 2 commits
    • Benjamin Eberlei's avatar
      Merge branch 'DBAL-2883' into 2.4 · 1b90a2eb
      Benjamin Eberlei authored
      1b90a2eb
    • José Gabriel González Pérez's avatar
      Fix statement for getTableWhereClause method · 02a1db65
      José Gabriel González Pérez authored
      If you have a role "postgres" in PostgreSQL that is described like this:
      ```
      -- Role: postgres
      CREATE ROLE postgres LOGIN
        ENCRYPTED PASSWORD 'md53175bce1d3201d16594cebf9d7eb3f9d'
        SUPERUSER INHERIT CREATEDB CREATEROLE REPLICATION;
      ALTER ROLE postgres IN DATABASE sf_test
        SET search_path = "$user", public, access, geographic, rrhh;
      ```
      
      At the time when I execute the statement (Part of $schema value in the line 348):
      ```
      SELECT string_to_array((select replace(replace(setting,"$user",user),' ','') from pg_catalog.pg_settings where name = 'search_path'),',')
      ```
      I fetch this result:
      ```
      {public," access"," geographic"," rrhh"}
      ```
      Look the space character that is on the start of each string.This error does not match any namespace to which the role has access. This is critical when you have PostgreSQL database and you work with schemas.
      02a1db65
  9. 03 Jan, 2014 4 commits
  10. 01 Jan, 2014 2 commits
  11. 31 Dec, 2013 8 commits
  12. 29 Dec, 2013 7 commits