1. 07 Nov, 2007 1 commit
  2. 12 Jun, 2007 1 commit
  3. 17 Feb, 2007 1 commit
  4. 16 Feb, 2007 3 commits
  5. 17 Oct, 2006 1 commit
    • Tom Lane's avatar
      Fix up some problems in handling of zic-style time zone names in datetime · 022fd996
      Tom Lane authored
      input routines.  Remove the former "DecodePosixTimezone" function in favor of
      letting the zic code handle POSIX-style zone specs (see tzparse()).  In
      particular this means that "PST+3" now means the same as "-03", whereas it
      used to mean "-11" --- the zone abbreviation is effectively just a noise word
      in this syntax.  Make sure that all named and POSIX-style zone names will be
      parsed as a single token.  Fix long-standing bogosities in printing and input
      of fractional-hour timezone offsets (since the tzparse() code will accept
      these, we'd better make 'em work).  Also correct an error in the original
      coding of the zic-zone-name patch: in "timestamp without time zone" input,
      zone names are supposed to be allowed but ignored, but the coding was such
      that the zone changed the interpretation anyway.
      022fd996
  6. 25 Jul, 2006 1 commit
    • Tom Lane's avatar
      Remove hard-wired lists of timezone abbreviations in favor of providing · d8b5c95c
      Tom Lane authored
      configuration files that can be altered by a DBA.  The australian_timezones
      GUC setting disappears, replaced by a timezone_abbreviations setting (set this
      to 'Australia' to get the effect of australian_timezones).  The list of zone
      names defined by default has undergone a bit of cleanup, too.  Documentation
      still needs some work --- in particular, should we fix Table B-4, or just get
      rid of it?  Joachim Wieland, with some editorializing by moi.
      d8b5c95c
  7. 06 Jul, 2006 1 commit
  8. 26 Jun, 2005 1 commit
  9. 05 Mar, 2004 1 commit
  10. 25 Dec, 2003 1 commit
    • Bruce Momjian's avatar
      > > I have no idea if this in Oracle or not. But it's something I · 1c757c49
      Bruce Momjian authored
      > > needed, and other people in the past asked about it too.
      >
      > It is in Oracle, but you aren't exactly on the spot.  It should be
      >
      > IYYY - 4 digits  ('2003')
      > IYY  - 3 digits  ('003')
      > IY   - 2 digits  ('03')
      > I    - 1 digit   ('3')
      
      Here is an updated patch that does that.
      
      Kurt Roeckx
      1c757c49
  11. 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
  12. 04 Oct, 2001 1 commit
  13. 03 Oct, 2001 1 commit
    • Thomas G. Lockhart's avatar
      Implement precision support for timestamp and time, both with and without · 3e1beda2
      Thomas G. Lockhart authored
       time zones.
      SQL99 spec requires a default of zero (round to seconds) which is set
       in gram.y as typmod is set in the parse tree. We *could* change to a
       default of either 6 (for internal compatibility with previous versions)
       or 2 (for external compatibility with previous versions).
      Evaluate entries in pg_proc wrt the iscachable attribute for timestamp and
       other date/time types. Try to recognize cases where side effects like the
       current time zone setting may have an effect on results to decide whether
       something is cachable or not.
      3e1beda2
  14. 28 Sep, 2001 1 commit