Re: Shouldn't default multibyte encoding come from template database?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Shouldn't default multibyte encoding come from template database?
Date: 2000-11-14 06:28:30
Message-ID: Pine.LNX.4.21.0011140725110.1116-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:

> I've got the multiple-template-database feature nearly ready to commit,
> but I was just noticing that the way we handle default MB encoding
> selection seems wrong for this way of looking at things. Currently,
> if you don't specify "ENCODING = something" in CREATE DATABASE, the
> default is to use the encoding that applies to the database you're
> currently connected to.

How so?

| CREATE DATABASE database_name
{
CreatedbStmt *n = makeNode(CreatedbStmt);
n->dbname = $3;
n->dbpath = NULL;
n->encoding = GetTemplateEncoding();
$$ = (Node *)n;
}

Or does GetTemplateEncoding() not get the template encoding?

In any case, it should, because that's how it used to work and how it's
documented.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-11-14 07:12:19 Re: FW: Returned mail: see transcript for details
Previous Message Tom Lane 2000-11-14 05:59:19 Re: SearchSysCacheTuple(Copy)