Skip to content
Snippets Groups Projects
  1. Jul 24, 1998
    • Marc G. Fournier's avatar
      · bf00bbb0
      Marc G. Fournier authored
      I really hope that I haven't missed anything in this one...
      
      From: t-ishii@sra.co.jp
      
      Attached are patches to enhance the multi-byte support.  (patches are
      against 7/18 snapshot)
      
      * determine encoding at initdb/createdb rather than compile time
      
      Now initdb/createdb has an option to specify the encoding. Also, I
      modified the syntax of CREATE DATABASE to accept encoding option. See
      README.mb for more details.
      
      For this purpose I have added new column "encoding" to pg_database.
      Also pg_attribute and pg_class are changed to catch up the
      modification to pg_database.  Actually I haved added pg_database_mb.h,
      pg_attribute_mb.h and pg_class_mb.h. These are used only when MB is
      enabled. The reason having separate files is I couldn't find a way to
      use ifdef or whatever in those files. I have to admit it looks
      ugly. No way.
      
      * support for PGCLIENTENCODING when issuing COPY command
      
      commands/copy.c modified.
      
      * support for SQL92 syntax "SET NAMES"
      
      See gram.y.
      
      * support for LATIN2-5
      * add UNICODE regression test case
      * new test suite for MB
      
      New directory test/mb added.
      
      * clean up source files
      
      Basic idea is to have MB's own subdirectory for easier maintenance.
      These are include/mb and backend/utils/mb.
      bf00bbb0
  2. Jun 16, 1998
    • Bruce Momjian's avatar
      Hi, here are the patches to enhance existing MB handling. This time · cb7cbc16
      Bruce Momjian authored
      I have implemented a framework of encoding translation between the
      backend and the frontend. Also I have added a new variable setting
      command:
      
      SET CLIENT_ENCODING TO 'encoding';
      
      Other features include:
      	Latin1 support more 8 bit cleaness
      
      See doc/README.mb for more details. Note that the pacthes are
      against May 30 snapshot.
      
      Tatsuo Ishii
      cb7cbc16
  3. Apr 27, 1998
    • Marc G. Fournier's avatar
      From: t-ishii@sra.co.jp · f554af0a
      Marc G. Fournier authored
      Hi, here are patches I promised (against 6.3.2):
      
      * character_length(), position(), substring() are now aware of
                multi-byte characters
      * add octet_length()
      * add --with-mb option to configure
      * new regression tests for EUC_KR
        (contributed by "Soonmyung. Hong" <hong@lunaris.hanmesoft.co.kr>)
      * add some test cases to the EUC_JP regression test
      * fix problem in regress/regress.sh in case of System V
      * fix toupper(), tolower() to handle 8bit chars
      
      note that:
      
      o  patches for both configure.in and configure are
      included. maybe the one for configure is not necessary.
      
      o pg_proc.h was modified to add octet_length(). I used OIDs
      (1374-1379) for that. Please let me know if these numbers are not
      appropriate.
      f554af0a
  4. Mar 15, 1998
    • Marc G. Fournier's avatar
      From: t-ishii@sra.co.jp · 661ecf3c
      Marc G. Fournier authored
      Included are patches intended for allowing PostgreSQL to handle
      multi-byte charachter sets such as EUC(Extende Unix Code), Unicode and
      Mule internal code. With the MB patch you can use multi-byte character
      sets in regexp and LIKE. The encoding system chosen is determined at
      the compile time.
      
      To enable the MB extension, you need to define a variable "MB" in
      Makefile.global or in Makefile.custom. For further information please
      take a look at README.mb under doc directory.
      
      (Note that unlike "jp patch" I do not use modified GNU regexp any
      more. I changed Henry Spencer's regexp coming with PostgreSQL.)
      661ecf3c
Loading