summaryrefslogtreecommitdiff
path: root/src/backend/utils/mb/variable.c
AgeCommit message (Collapse)Author
2000-10-25Support SET/SHOW/RESET client_encoding and server_encoding even whenTom Lane
MULTIBYTE support is not compiled (you just can't set them to anything but SQL_ASCII). This should reduce interoperability problems between MB-enabled clients and non-MB-enabled servers.
2000-04-20Clean up const-vs-not-const compiler warning in MULTIBYTE code.Tom Lane
'Twas my fault, I think.
2000-01-18Fix minor comping errorsTatsuo Ishii
1999-07-17Fix for multi-byte includes.Bruce Momjian
1999-05-25pgindent run over code.Bruce Momjian
1999-05-13set client_encoding to <nothing> crashes backend.Tatsuo Ishii
1998-09-01OK, folks, here is the pgindent output.Bruce Momjian
1998-07-24I really hope that I haven't missed anything in this one...Marc G. Fournier
From: [email protected] 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.