Re: [WIP] patch - Collation at database level - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [WIP] patch - Collation at database level
Date
Msg-id 20080702151423.GT18252@alvh.no-ip.org
Whole thread Raw
In response to [WIP] patch - Collation at database level  ("Radek Strnad" <radek.strnad@gmail.com>)
Responses Re: [WIP] patch - Collation at database level  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Radek Strnad escribió:

> 2) What type should all names in CREATE and DROP statement in gram.y have?
> I've chosen qualified_name but I know it's not the best choice.

I think it should be ColId.

> 3) All collations are created from existing collations. How do I ensure that
> the collation already exists? Is there any possibility to define it in
> gram.y?

Certainly not -- shouldn't they come from a catalog?  In that case, it
must come in parse analysis (parser/analyze.c I guess) or perhaps later,
when you actually execute the function to create the new collation.

> 5) Also can you look at the pg_catalog and tell me if anything is wrong with
> it?

Why does a collation have a schema?

What's the "existing collation"?

It seems a bit silly to have enum for what are basically boolean
variables.  Why not just use "true" and "false"?
-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: WIP patch: reducing overhead for repeat de-TOASTing
Next
From: Zdenek Kotala
Date:
Subject: Re: PATCH: CITEXT 2.0