1. 29 Jul, 2003 1 commit
    • Tom Lane's avatar
      Apply (a somewhat revised version of) Greg Mullane's patch to eliminate · 9c2a7c22
      Tom Lane authored
      heuristic determination of day vs month in date/time input.  Add the
      ability to specify that input is interpreted as yy-mm-dd order (which
      formerly worked, but only for yy greater than 31).  DateStyle's input
      component now has the preferred spellings DMY, MDY, or YMD; the older
      keywords European and US are now aliases for the first two of these.
      Per recent discussions on pgsql-general.
      9c2a7c22
  2. 27 Jul, 2003 1 commit
  3. 22 Jul, 2003 1 commit
  4. 09 Jul, 2003 1 commit
  5. 04 Jul, 2003 1 commit
  6. 20 Jun, 2003 1 commit
  7. 11 Jun, 2003 1 commit
  8. 27 May, 2003 1 commit
  9. 14 May, 2003 2 commits
  10. 12 May, 2003 1 commit
  11. 09 May, 2003 2 commits
  12. 08 May, 2003 2 commits
  13. 06 May, 2003 6 commits
  14. 05 May, 2003 1 commit
  15. 03 May, 2003 2 commits
  16. 02 May, 2003 3 commits
  17. 29 Apr, 2003 1 commit
    • Tom Lane's avatar
      Infrastructure for deducing Param types from context, in the same way · aa282d44
      Tom Lane authored
      that the types of untyped string-literal constants are deduced (ie,
      when coerce_type is applied to 'em, that's what the type must be).
      Remove the ancient hack of storing the input Param-types array as a
      global variable, and put the info into ParseState instead.  This touches
      a lot of files because of adjustment of routine parameter lists, but
      it's really not a large patch.  Note: PREPARE statement still insists on
      exact specification of parameter types, but that could easily be relaxed
      now, if we wanted to do so.
      aa282d44
  18. 27 Apr, 2003 1 commit
    • Tom Lane's avatar
      Put back encoding-conversion step in processing of incoming queries; · 982430f8
      Tom Lane authored
      I had inadvertently omitted it while rearranging things to support
      length-counted incoming messages.  Also, change the parser's API back
      to accepting a 'char *' query string instead of 'StringInfo', as the
      latter wasn't buying us anything except overhead.  (I think when I put
      it in I had some notion of making the parser API 8-bit-clean, but
      seeing that flex depends on null-terminated input, that's not really
      ever gonna happen.)
      982430f8
  19. 24 Apr, 2003 1 commit
    • Tom Lane's avatar
      Infrastructure for upgraded error reporting mechanism. elog.c is · f690920a
      Tom Lane authored
      rewritten and the protocol is changed, but most elog calls are still
      elog calls.  Also, we need to contemplate mechanisms for controlling
      all this functionality --- eg, how much stuff should appear in the
      postmaster log?  And what API should libpq expose for it?
      f690920a
  20. 22 Apr, 2003 1 commit
    • Tom Lane's avatar
      Another round of protocol changes. Backend-to-frontend messages now all · 5ed27e35
      Tom Lane authored
      have length words.  COPY OUT reimplemented per new protocol: it doesn't
      need \. anymore, thank goodness.  COPY BINARY to/from frontend works,
      at least as far as the backend is concerned --- libpq's PQgetline API
      is not up to snuff, and will have to be replaced with something that is
      null-safe.  libpq uses message length words for performance improvement
      (no cycles wasted rescanning long messages), but not yet for error
      recovery.
      5ed27e35
  21. 19 Apr, 2003 1 commit
  22. 17 Apr, 2003 1 commit
  23. 24 Mar, 2003 1 commit
  24. 22 Mar, 2003 1 commit
  25. 20 Mar, 2003 1 commit
    • Bruce Momjian's avatar
      Todo items: · 5f65225f
      Bruce Momjian authored
      Add ALTER SEQUENCE to modify min/max/increment/cache/cycle values
      
      Also updated create sequence docs to mention NO MINVALUE, & NO MAXVALUE.
      
      New Files:
      doc/src/sgml/ref/alter_sequence.sgml
      src/test/regress/expected/sequence.out
      src/test/regress/sql/sequence.sql
      
      
      ALTER SEQUENCE is NOT transactional.  It behaves similarly to setval().
      It matches the proposed SQL200N spec, as well as Oracle in most ways --
      Oracle lacks RESTART WITH for some strange reason.
      
      --
      Rod Taylor <rbt@rbt.ca>
      5f65225f
  26. 10 Mar, 2003 1 commit
    • Tom Lane's avatar
      Restructure parsetree representation of DECLARE CURSOR: now it's a · aa83bc04
      Tom Lane authored
      utility statement (DeclareCursorStmt) with a SELECT query dangling from
      it, rather than a SELECT query with a few unusual fields in it.  Add
      code to determine whether a planned query can safely be run backwards.
      If DECLARE CURSOR specifies SCROLL, ensure that the plan can be run
      backwards by adding a Materialize plan node if it can't.  Without SCROLL,
      you get an error if you try to fetch backwards from a cursor that can't
      handle it.  (There is still some discussion about what the exact
      behavior should be, but this is necessary infrastructure in any case.)
      Along the way, make EXPLAIN DECLARE CURSOR work.
      aa83bc04
  27. 06 Mar, 2003 1 commit
  28. 10 Feb, 2003 1 commit
  29. 01 Jan, 2003 1 commit