From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Valerie Cole <valerie(dot)cole(at)wirestone(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Question regarding Hibernate ORDER BY issue |
Date: | 2007-10-20 00:59:11 |
Message-ID: | 20071020005911.GB24660@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Valerie Cole wrote:
> I have a problem and am pretty sure Hibernate is the culprit but was
> wondering if anybody knew of a fix. We are working on legacy code and
> converted a class from Hibernate 2 xml mappings to Hibernate 3 with
> annotations. On one of the One To Many attributes we have used the
> @OrderBy("displayPosition"). The SQL generated by Hibernate outputs the
> column name as DisplayPosition with no quoting, and Postgres kicks back
> an error saying the column does not exist.
Did you try adding extra double quotes? Something like
@OrderBy("\"displayPosition\"").
> Our tables/columns have all been created with quotes and must be
> accessed with quotes (I don't know if that is the norm, I am somewhat
> of a Postgres newb).
This is correct, unless your table/column names (a.k.a. "identifiers")
are lowercase in which case you can leave the quotes out.
--
Alvaro Herrera http://www.flickr.com/photos/alvherre/
A male gynecologist is like an auto mechanic who never owned a car.
(Carrie Snow)
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-10-20 01:05:55 | Re: ERROR: Could not access status of transaction #### |
Previous Message | Josh Trutwin | 2007-10-20 00:11:31 | Re: Questions about LIMIT/OFFSET |