| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Adam Hardy <adam(dot)hardy(at)cyberspaceroad(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #3894: JDBC DatabaseMetaData.getTables is inconsistently case-sensitive with schema name |
| Date: | 2008-02-12 16:40:21 |
| Message-ID: | Pine.BSO.4.64.0802121137520.13441@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg윈 토토SQL : Postg윈 토토SQL 메일 링리스트 : 2008-02-12 이후 PGSQL-BUGS 16:40 |
On Tue, 12 Feb 2008, Adam Hardy wrote:
> Because this rules out certain important features of the JPA framework such
> as native SQL queries, you may want to prioritize this issue. I will have to
> use Oracle or mySQL until PostgreSQL can rectify things.
I wouldn't expect postgresql to change anytime soon. Could you explain in
more detail what you can't use and why the JPA side couldn't be fixed to
support postgresql?
You could also consider always quoting all identifiers in both database
creation scripts and queries. This guarantees that the database won't
mess with the case of the object although it can be a pain to type if you
writing a lot of queries by hand.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Ivanov | 2008-02-12 17:36:05 | BUG #3956: COPY FROM doesn't parse file correctly |
| Previous Message | Adam Hardy | 2008-02-12 15:10:19 | Re: BUG #3894: JDBC DatabaseMetaData.getTables is inconsistently case-sensitive with schema name |