[ckan-changes] [ckan/ckan] d0d0fa: Note for sql searches with UPPERCASE column names

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/ckan/ckan
  Commit: d0d0fa3fff517a945a76ce008d16b4e98dae35c3
      https://github.com/ckan/ckan/commit/d0d0fa3fff517a945a76ce008d16b4e98dae35c3
  Author: Cam Findlay <info at camfindlay.com>
  Date:   2018-01-05 (Fri, 05 Jan 2018)

  Changed paths:
    M ckanext/datastore/logic/action.py

  Log Message:
  -----------
  Note for sql searches with UPPERCASE column names

Something we found when using the datastore_search_sql API call was that in situations where the source data headings were all uppercase, the sql would return no results (even though we knew results should show). We eventually traced this to some postgres related config around uppercase identifiers. Solution is to double quote the column name. Adding here to document for future reference incase others get stumped by this. 

Tested in CKAN 2.6.0, 2.6.4 you may want to backport this note into some of the older docs.

Original ckan-dev list reference about this at: https://lists.okfn.org/pipermail/ckan-dev/2017-November/011201.html


  Commit: ae12f82dbf35fc0dbbac37a37fa26e2bb163a7c6
      https://github.com/ckan/ckan/commit/ae12f82dbf35fc0dbbac37a37fa26e2bb163a7c6
  Author: Adrià Mercader <amercadero at gmail.com>
  Date:   2018-01-09 (Tue, 09 Jan 2018)

  Changed paths:
    M ckanext/datastore/logic/action.py

  Log Message:
  -----------
  Merge pull request #3975 from camfindlay/patch-1

DOCS Note for sql searches with UPPERCASE column names


Compare: https://github.com/ckan/ckan/compare/7506353cc465...ae12f82dbf35