From: | "Simpson, Mike W" <mike(dot)simpson(at)pbs(dot)proquest(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: [JDBC] Performance problem iterating a resultset |
Date: | 2002-10-18 15:40:03 |
Message-ID: | 560796A29B821F40A277973FB5EA300496FAA2@slexc1a.server.power.bellhow.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
Can someone confirm for me that the back end doesn't support parameters in
the order by clause for jdbc prepared statements? I error out through JDBC
and through pgadmin when attempting to create one:
this works:
PREPARE JDBC_STATEMENT_100(text) AS
SELECT partid from parts ORDER BY partid;
this errors out with "parse error at or near ";" at character 72":
PREPARE JDBC_STATEMENT_100(text) AS
SELECT partid from parts ORDER BY ?;
this errors out with "Non-integer constant in ORDER BY":
PREPARE JDBC_STATEMENT_100(text) AS
SELECT partid from parts ORDER BY '?';
Anyone shed some light on this for me?
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-10-18 15:41:39 | Re: pg_attribute always grow... |
Previous Message | Stephan Szabo | 2002-10-18 15:12:59 | Re: referential integrity violation |
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-10-18 17:44:38 | Re: problem with the build file? |
Previous Message | Dave Cramer | 2002-10-18 14:34:26 | Re: [JDBC] Performance problem iterating a resultset |