1. 26 5月, 2014 1 次提交
  2. 20 5月, 2014 1 次提交
  3. 19 5月, 2014 1 次提交
  4. 14 5月, 2014 1 次提交
  5. 04 4月, 2014 1 次提交
  6. 15 3月, 2014 1 次提交
  7. 18 1月, 2014 1 次提交
  8. 17 1月, 2014 1 次提交
  9. 24 3月, 2013 1 次提交
  10. 14 10月, 2012 1 次提交
    • A
      #7914 get default value when type uses schema name · 2da85edd
      Arturo Pie 提交于
      PostgreSQL adapter properly parses default values when using multiple
      schemas and domains.
      
      When using domains across schemas, PostgresSQL prefixes the type of the
      default value with the name of the schema where that type (or domain) is.
      
      For example, this query:
      ```
      SELECT a.attname, d.adsrc
      FROM pg_attribute a LEFT JOIN pg_attrdef d
      ON a.attrelid = d.adrelid AND a.attnum = d.adnum
      WHERE a.attrelid = "defaults"'::regclass
      AND a.attnum > 0 AND NOT a.attisdropped
      ORDER BY a.attnum;
      ```
      
      could return something like "'<default_value>'::pg_catalog.text" or
      "(''<default_value>'::pg_catalog.text)::text" for the text columns with
      defaults.
      
      I modified the regexp used to parse this value so that it ignores
      anything between ':: and \b(?:character varying|bpchar|text), and it
      allows to have optional parens like in the above second example.
      2da85edd
  11. 12 10月, 2012 1 次提交
  12. 08 3月, 2012 1 次提交
  13. 07 3月, 2012 1 次提交
  14. 20 2月, 2012 1 次提交
  15. 04 12月, 2011 1 次提交
  16. 30 11月, 2011 1 次提交
  17. 17 11月, 2011 1 次提交
  18. 07 11月, 2011 1 次提交
  19. 05 11月, 2011 1 次提交
  20. 19 10月, 2011 1 次提交
  21. 06 10月, 2011 1 次提交
  22. 08 9月, 2011 1 次提交
  23. 09 7月, 2011 1 次提交
  24. 08 7月, 2011 1 次提交
  25. 19 6月, 2011 1 次提交
  26. 11 6月, 2011 2 次提交
  27. 10 6月, 2011 2 次提交
    • P
      apply private method indentation convention · 019c2636
      Paul Gallagher 提交于
      * tidy test code and fix my typo 
      019c2636
    • P
      Improve PostgreSQL adapter schema-awareness · 5c7f8c92
      Paul Gallagher 提交于
      * table_exists? scoped by schema search path unless schema is explicitly named. Added tests and doc to clarify the behaviour
      * extract_schema_and_table tests and implementation extended to cover all cases
      * primary_key does not ignore schema information
      * add current_schema and schema_exists? methods
      * more robust table referencing in insert_sql and sql_for_insert methods
      5c7f8c92
  28. 07 6月, 2011 1 次提交
  29. 05 6月, 2011 1 次提交
    • J
      Refactor Active Record test connection setup. Please see the... · 253bb6b9
      Jon Leighton 提交于
      Refactor Active Record test connection setup. Please see the RUNNING_UNIT_TESTS file for details, but essentially you can now configure things in test/config.yml. You can also run tests directly via the command line, e.g. ruby path/to/test.rb (no rake needed, uses default db connection from test/config.yml). This will help us fix the CI by enabling us to isolate the different Rails versions to different databases.
      253bb6b9
  30. 26 6月, 2010 2 次提交
  31. 19 5月, 2010 1 次提交
  32. 12 4月, 2010 1 次提交
  33. 21 4月, 2009 2 次提交
  34. 05 4月, 2009 1 次提交
  35. 03 3月, 2008 1 次提交
  36. 22 1月, 2008 1 次提交