1. 25 Jun, 2002 1 commit
  2. 06 Jun, 2002 1 commit
  3. 04 Apr, 2002 1 commit
  4. 29 Mar, 2002 1 commit
  5. 28 Mar, 2002 1 commit
    • Hiroshi Inoue's avatar
      [2002-03-28] · 6852741c
      Hiroshi Inoue authored
      1) Prepare to separate 4 kinds of Descriptor handles.
      2) Detect the transaction status more naturally.
      3) Improve Parse Statement functionality for the use
         of updatable cursors.
      4) Improve updatable cursors.
      5) Implement SQLGetDescField() and improve SQLColAttribute().
      6) etc.
      6852741c
  6. 25 Mar, 2002 1 commit
  7. 14 Mar, 2002 1 commit
  8. 08 Mar, 2002 2 commits
    • Hiroshi Inoue's avatar
      Remove compile errors. · fc701047
      Hiroshi Inoue authored
      fc701047
    • Hiroshi Inoue's avatar
      1) Implement SQLParamOptions(). · 4b47467a
      Hiroshi Inoue authored
      2) Handle Multiple results and implement SQLMoreResult().
      3) Improve multibyte handling thanks to Eiji Tokuya.
      4) Add new options.
         LF <-> CR/LF converion.
         TRUE is -1 (for VB).
      5) Introduce unicode(UCS-2) support.
      6) Reduce the length of connection strings.
      7) Improve SQLError, SQLGetDiagRec(ODBC 3.0).
      8) Implement SQLTablePrivileges().
      9) Miscellaneous changes for ODBC 3.0 support.
      4b47467a
  9. 05 Mar, 2002 1 commit
    • Bruce Momjian's avatar
      > Tatsuo Ishii wrote: · a8bd7e1c
      Bruce Momjian authored
      > > > > It was made to cope with encoding such as an Asian bloc in 7.2Beta2.
      > > > >
      > > > > Added ServerEncoding
      > > > >         Korean (JOHAB), Thai (WIN874),
      > > > >         Vietnamese (TCVN), Arabic (WIN1256)
      > > > >
      > > > > Added ClientEncoding
      > > > >         Simplified Chinese (GBK), Korean (UHC)
      > > > >
      > > > >
      > > > >
      > http://www.sankyo-unyu.co.jp/Pool/postgresql-7.2b2.newencoding.diff.tar.gz
      > > > > (608K)
      > > >
      > > > Looks good.  I need some people to review this for me.
      > >
      > > For me they look good too. The only missing part is a
      > > documentation. I will ask him to write it up. If he couldn't, I will
      > > do it for him.
      > > > The diff is 3mb
      > > > but appears to address only additions to multibyte.  I have attached a
      > > > list of files it modifies.  Also, look at the sizes of the mb/
      > > > directory.  It is getting large:
      > > >
      > > >   4       ./CVS
      > > >   6       ./Unicode/CVS
      > > >   3433    ./Unicode
      > > >   6197    .
      > >
      > > Yes. We definitely need the on-the-fly encoding addition capability:
      > > i.e. CREATE CHRACTER SET in the future...
      > > --
      > > Tatsuo Ishii
      > >
      > >
      
      Address chainge.
      
      http://www.sankyo-unyu.co.jp/Pool/postgresql-7.2.newencoding.diff.gz
      
      Add PsqlODBC and document ...etc patch.
      
      Eiji Tokuya
      a8bd7e1c
  10. 18 Feb, 2002 1 commit
  11. 25 Oct, 2001 1 commit
  12. 07 Sep, 2001 1 commit
  13. 06 Sep, 2001 2 commits
    • Tatsuo Ishii's avatar
      Fix Karel's patch. Suggested by Eiji Tokuya · f25ed23c
      Tatsuo Ishii authored
      f25ed23c
    • Tatsuo Ishii's avatar
      Commit Karel's patch. · 22776711
      Tatsuo Ishii authored
      -------------------------------------------------------------------
      Subject: Re: [PATCHES] encoding names
      From: Karel Zak <zakkr@zf.jcu.cz>
      To: Peter Eisentraut <peter_e@gmx.net>
      Cc: pgsql-patches <pgsql-patches@postgresql.org>
      Date: Fri, 31 Aug 2001 17:24:38 +0200
      
      On Thu, Aug 30, 2001 at 01:30:40AM +0200, Peter Eisentraut wrote:
      > > 		- convert encoding 'name' to 'id'
      >
      > I thought we decided not to add functions returning "new" names until we
      > know exactly what the new names should be, and pending schema
      
       Ok, the patch not to add functions.
      
      > better
      >
      >     ...(): encoding name too long
      
       Fixed.
      
       I found new bug in command/variable.c in parse_client_encoding(), nobody
      probably never see this error:
      
      if (pg_set_client_encoding(encoding))
      {
      	elog(ERROR, "Conversion between %s and %s is not supported",
                           value, GetDatabaseEncodingName());
      }
      
      because pg_set_client_encoding() returns -1 for error and 0 as true.
      It's fixed too.
      
       IMHO it can be apply.
      
      		Karel
      PS:
      
          * following files are renamed:
      
      src/utils/mb/Unicode/KOI8_to_utf8.map  -->
              src/utils/mb/Unicode/koi8r_to_utf8.map
      
      src/utils/mb/Unicode/WIN_to_utf8.map  -->
              src/utils/mb/Unicode/win1251_to_utf8.map
      
      src/utils/mb/Unicode/utf8_to_KOI8.map -->
              src/utils/mb/Unicode/utf8_to_koi8r.map
      
      src/utils/mb/Unicode/utf8_to_WIN.map -->
              src/utils/mb/Unicode/utf8_to_win1251.map
      
         * new file:
      
      src/utils/mb/encname.c
      
         * removed file:
      
      src/utils/mb/common.c
      
      --
       Karel Zak  <zakkr@zf.jcu.cz>
       http://home.zf.jcu.cz/~zakkr/
      
       C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
      22776711
  14. 24 Aug, 2001 1 commit
  15. 08 May, 2001 2 commits
  16. 27 Mar, 2001 1 commit
  17. 22 Mar, 2001 2 commits
  18. 21 Mar, 2001 1 commit
  19. 16 Mar, 2001 1 commit