1. 22 Jul, 2000 1 commit
  2. 18 Apr, 2000 4 commits
  3. 17 Dec, 1999 1 commit
  4. 14 Dec, 1999 1 commit
    • Bruce Momjian's avatar
      Depending on my interpreting (and programming) skills, this might solve · bcaabc56
      Bruce Momjian authored
      anywhere from zero to two TODO items.
      
      * Allow flag to control COPY input/output of NULLs
      
      I got this:
      COPY table .... [ WITH NULL AS 'string' ]
      which does what you'd expect. The default is \N, otherwise you can use
      empty strings, etc. On Copy In this acts like a filter: every data item
      that looks like 'string' becomes a NULL. Pretty straightforward.
      
      This also seems to be related to
      
      * Make postgres user have a password by default
      
      If I recall this discussion correctly, the problem was actually that the
      default password for the postgres (or any) user is in fact "\N", because
      of the way copy is used. With this change, the file pg_pwd is copied out
      with nulls as empty strings, so if someone doesn't have a password, the
      password is just '', which one would expect from a new account. I don't
      think anyone really wants a hard-coded default password.
      
      Peter Eisentraut                  Sernanders väg 10:115
      bcaabc56
  5. 29 Oct, 1999 1 commit
  6. 22 Jul, 1999 1 commit
  7. 06 Jul, 1999 1 commit
  8. 13 Feb, 1999 1 commit
  9. 02 Feb, 1999 1 commit
  10. 29 Dec, 1998 1 commit
  11. 30 Oct, 1998 1 commit
  12. 16 Sep, 1998 1 commit
  13. 07 Sep, 1998 1 commit
  14. 13 May, 1998 1 commit