From: | "David Hooker" <dhooker(at)a4networks(dot)com> |
---|---|
To: | <Hale(at)halepringle(dot)com>, <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL/Oracle/MSSQL differences (was: streaming result |
Date: | 2002-11-15 17:35:20 |
Message-ID: | 003401c28ccd$5ec29530$5c0a0a0a@dhooker |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Just ran into another one. PostgreSQL creates tables as all lowercase,
even if the SQL statement is in uppercase. Since I'm using the
pg_tables view to check for the existance of tables, this makes the case
in the WHERE clause significant. Oracle forces everything to uppercase.
PostgreSQL forces everything to lowercase. Argh!!
-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org] On Behalf Of Hale Pringle
Sent: Thursday, November 14, 2002 4:31 PM
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] PostgreSQL/Oracle/MSSQL differences (was: streaming
result
One big difference that you should look for is case sensitivity in WHERE
clauses. I know that SQL-SERVER defaults to case-insensitive and you
have
to go through hoops to do a case sensitive search. PostreSQL defaults
to
case sensitive and uses the non-standard "ILIKE" verb to generate a
case-insensitive WHERE clause.
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-11-15 18:36:42 | Re: OID-problem: metadata: use of TableGen O/R-mapper |
Previous Message | Lloyd Meinholz | 2002-11-15 17:34:55 | Re: postgreSQL 7.2.3: jdbc compile problem |