From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
---|---|
To: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Exposing keywords to clients |
Date: | 2008-05-02 20:54:56 |
Message-ID: | 937d27e10805021354s70b24c0l29f7f18dc0ad0ec9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Hi,
The attached patch implements a new function, pg_get_keywords(), which
returns a set of records describing the keywords recognised by the
server. This allows clients such as pgAdmin to get quoting rules
correct, and helps with other tasks such as syntax highlighting where
we need to support multiple server versions.
Example output (edited of course):
postgres=# select * from pg_get_keywords();
word | category
-------------------+-----------------------
all | Reserved
binary | Type or function name
xmlserialize | Column name
zone | Unreserved
(372 rows)
I wasn't sure about the best way to describe the categories -
obviously they need to be non-translatable (for client software to
interpret), but human readable is also nice. I'm happy to hear
alternate suggestions.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
pg_get_keywords.diff | text/plain | 6.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-05-02 21:13:38 | Re: [HACKERS] GUC parameter cursors_tuple_fraction |
Previous Message | Simon Riggs | 2008-05-02 20:49:39 | Re: [HACKERS] GUC parameter cursors_tuple_fraction |