1. 05 Dec, 2002 1 commit
  2. 23 Nov, 2002 1 commit
  3. 21 Nov, 2002 1 commit
  4. 11 Nov, 2002 1 commit
  5. 24 Oct, 2002 1 commit
  6. 05 Oct, 2002 2 commits
  7. 24 Sep, 2002 1 commit
  8. 22 Sep, 2002 1 commit
  9. 21 Sep, 2002 1 commit
  10. 20 Sep, 2002 1 commit
  11. 12 Sep, 2002 1 commit
    • Bruce Momjian's avatar
      Joe Conway wrote: · 81186865
      Bruce Momjian authored
       > Hannu Krosing wrote:
       >
       >> It seems that my last mail on this did not get through to the list
       >> ;(
       >>
       >> Please consider renaming the new builtin function
       >> split(text,text,int)
       >>
       >> to something else, perhaps
       >>
       >> split_part(text,text,int)
       >>
       >> (like date_part)
       >>
       >> The reason for this request is that 3 most popular scripting
       >> languages (perl, python, php) all have also a function with similar
       >> signature, but returning an array instead of single element and the
       >> (optional) third argument is limit (maximum number of splits to
       >> perform)
       >>
       >> I think that it would be good to have similar function in (some
       >> future release of) postgres, but if we now let in a function with
       >> same name and arguments but returning a single string instead an
       >> array of them, then we will need to invent a new and not so easy to
       >> recognise name for the "real" split function.
       >>
       >
       > This is a good point, and I'm not opposed to changing the name, but
       > it is too bad your original email didn't get through before beta1 was
       >  rolled. The change would now require an initdb, which I know we were
       >  trying to avoid once beta started (although we could change it
       > without *requiring* an initdb I suppose).
       >
       > I guess if we do end up needing an initdb for other reasons, we
       > should make this change too. Any other opinions? Is split_part an
       > acceptable name?
       >
       > Also, if we add a todo to produce a "real" split function that
       > returns an array, similar to those languages, I'll take it for 7.4.
      
      No one commented on the choice of name, so the attached patch changes
      the name of split(text,text,int) to split_part(text,text,int) per
      Hannu's recommendation above. This can be applied without an initdb if
      current beta testers are advised to run:
      
         update pg_proc set proname = 'split_part' where proname = 'split';
      
      in the case they want to use this function. Regression and doc fix is
      also included in the patch.
      
      Joe Conway
      81186865
  12. 11 Sep, 2002 1 commit
  13. 02 Sep, 2002 1 commit
  14. 01 Sep, 2002 1 commit
  15. 29 Aug, 2002 1 commit
  16. 22 Aug, 2002 2 commits
  17. 21 Aug, 2002 2 commits
  18. 20 Aug, 2002 1 commit
    • Bruce Momjian's avatar
      · de9801fc
      Bruce Momjian authored
      Add current_database().
      
      > Quick system function to pull out the current database.
      >
      > I've used this a number of times to allow stored procedures to find out
      > where they are.  Especially useful for those that do logging or hit a
      > remote server.
      >
      > It's called current_database() to match with current_user().
      
      It's also a necessity for an informational schema.  The catalog
      (database) name is required in a number of places.
      
      Rod Taylor
      de9801fc
  19. 16 Aug, 2002 1 commit
  20. 14 Aug, 2002 1 commit
  21. 09 Aug, 2002 1 commit
    • Tom Lane's avatar
      has_table_privilege spawns scions has_database_privilege, has_function_privilege, · 4ab8e690
      Tom Lane authored
      has_language_privilege, has_schema_privilege to let SQL queries test
      all the new privilege types in 7.3.  Also, add functions pg_table_is_visible,
      pg_type_is_visible, pg_function_is_visible, pg_operator_is_visible,
      pg_opclass_is_visible to test whether objects contained in schemas are
      visible in the current search path.  Do some minor cleanup to centralize
      accesses to pg_database, as well.
      4ab8e690
  22. 08 Aug, 2002 1 commit
  23. 06 Aug, 2002 1 commit
  24. 04 Aug, 2002 2 commits
  25. 31 Jul, 2002 1 commit
  26. 24 Jun, 2002 1 commit
  27. 15 Jun, 2002 2 commits
    • Bruce Momjian's avatar
      Patch for current_schemas to optionally include implicit ... · eb1ad5b4
      Bruce Momjian authored
      Second cut attached. This one just adds a boolean option to the existing
      function to indicate that implicit schemas are to be included (or not).
      I remembered the docs as well this time :-)
      
      Dave Page
      eb1ad5b4
    • Thomas G. Lockhart's avatar
      Add LOCALTIME and LOCALTIMESTAMP functions per SQL99 standard. · 133df7ce
      Thomas G. Lockhart authored
      Remove ODBC-compatible empty parentheses from calls to SQL99 functions
       for which these parentheses do not match the standard.
      Update the ODBC driver to ensure compatibility with the ODBC standard
       for these functions (e.g. CURRENT_TIMESTAMP, CURRENT_USER, etc).
      Include a new appendix in the User's Guide which lists the labeled features
       for SQL99 (the labeled features replaced the "basic", "intermediate",
       and "advanced" categories from SQL92). features.sgml does not yet split
       this list into "supported" and "unsupported" lists.
      133df7ce
  28. 11 Jun, 2002 2 commits
    • Thomas G. Lockhart's avatar
      Fix markup typo. · 062d8b9e
      Thomas G. Lockhart authored
      062d8b9e
    • Thomas G. Lockhart's avatar
      Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. · 090dd22d
      Thomas G. Lockhart authored
      Implement SQL99 SIMILAR TO as a synonym for our existing operator "~".
      Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape).
       Extend the definition to make the FOR clause optional.
       Define textregexsubstr() to actually implement this feature.
      Update the regression test to include these new string features.
       All tests pass.
      Rename the regular expression support routines from "pg95_xxx" to "pg_xxx".
      Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
      090dd22d
  29. 02 Jun, 2002 1 commit
  30. 18 May, 2002 1 commit
  31. 13 May, 2002 1 commit
  32. 26 Apr, 2002 1 commit
  33. 18 Apr, 2002 1 commit
    • Tom Lane's avatar
      Rule names are now unique per-relation, rather than unique globally. · b3120804
      Tom Lane authored
      DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause,
      similar to TRIGGER syntaxes.  To allow loading of existing pg_dump
      files containing COMMENT ON RULE, the COMMENT code will still accept
      the old syntax --- but only if the target rulename is unique across
      the whole database.
      b3120804
  34. 22 Mar, 2002 1 commit