From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SQL99, CREATE CAST, and initdb |
Date: | 2002-06-22 02:11:32 |
Message-ID: | 3D13DCD4.9D068BCB@fourpalms.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I've gone ahead and committed patches for CREATE CAST/DROP CAST, as well
as for a few other SQL99 clauses in other statements. Details below...
- Thomas
Implement SQL99 CREATE CAST and DROP CAST statements.
Also implement alternative forms to expose the PostgreSQL CREATE
FUNCTION
features.
Implement syntax for READ ONLY and READ WRITE clauses in SET
TRANSACTION.
READ WRITE is already implemented (of course).
Implement syntax for "LIKE table" clause in CREATE TABLE. Should be
fairly
easy to complete since it resembles SELECT INTO.
Implement MATCH SIMPLE clause for foreign key definitions. This is
explicit
SQL99 syntax for the default behavior, so we now support it :)
Start implementation of shorthand for national character literals in
scanner. For now, just swallow the leading "N", but sometime soon let's
figure out how to pass leading type info from the scanner to the
parser.
We should use the same technique for binary and hex bit string
literals,
though it might be unusual to have two apparently independent literal
types fold into the same storage type.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Loftis | 2002-06-22 02:17:22 | Re: What is wrong with hashed index usage? |
Previous Message | David Ford | 2002-06-22 02:10:37 | Re: What is wrong with hashed index usage? |