Colin,
Whether it is better or not isn't the issue. That is how the SQL
standard says it is supposed to work. If you create the objects with
quoted mixed case identifiers you must use quoted mixed case identifiers
to access the objects. A better solution to your problem would be to
create the tables without using quoted indentifiers and then your
original query would work.
thanks,
--Barry
Colin Freas wrote:
>>via quoted mixed case identifiers. I haven't seen any evidence that
>>basic SQL operations (select, insert, update, delete) have a bug in them.
>>
>
> I'd peg a where clause as a basic SQL operation, and be it bug, feature,
> annoyance, whatever, it wasn't functioning because of the case of a column
> name.
>
> This worked:
> 1. rs = stmt.executeQuery("select * from response");
>
> But I wanted to do this, which didn't work:
> 2. rs = stmt.executeQuery("select * from response where questionID=16");
>
> This is how I got it to work:
> 3. rs = stmt.executeQuery("SELECT \"response\".\"questionID\",
> \"response\".\"respondentID\", \"response\".\"answer\", \"response\".\"ID\"
> FROM \"response\" WHERE "\response\".\"questionID\"=16");
>
> Sorry, does anyone think the third is better than the second?
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>