| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Giuseppe Sacco <giuseppe(at)eppesuigoccas(dot)homedns(dot)org> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: DatabaseMetaData.getExtraNameCharacters |
| Date: | 2005-05-25 17:08:51 |
| Message-ID: | Pine.BSO.4.56.0505251204190.29241@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wed, 25 May 2005, Giuseppe Sacco wrote:
> We are developing a very simple application that permits users to define
> their own tables. We would like to leave the user the freedom to use any
> characters for table and field identifiers.
>
> We tried using accented letters, like è or ò, and it works. Then we saw
> the method java.sql.DatabaseMetaData.getExtraNameCharacters() and we
> thought about verifing our identifiers against this method.
>
> The problem is that getExtraNameCharacters() returns an empty string, at
> least using a 7.4 jdbc driver.
>
Postgresql allows pretty much any character that is valid in your encoding
to be used in an unquoted identifier, so trying to list them all would be
impossible, but there should be no problem using them.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2005-05-25 17:49:34 | Re: BIGINT <-> java.lang.String auto cast |
| Previous Message | Giuseppe Sacco | 2005-05-25 15:13:43 | DatabaseMetaData.getExtraNameCharacters |