safe, but not nearly as performant as the 'select 1' varities.
---- Cris J H
George Lindholm wrote:
Cris J Holdorph wrote:
I think the change in UP-1771 should be rolled back, until a better
more cross-database solution is developed. At least the major dbs
that most uPortal deployers are using (postgres, mysql, sql server,
oracle and HSQLDB for development).
The ultimate safe query would be "SELECT user_id FROM up_user WHERE
user_id = 1"
George
---- Cris J H
Eric Dalquist wrote:
As good as a default validation query should be perhaps just a
comment in the XML file with a few examples? Having to deal with
figuring out what sort of query you need for your specific DB just to
develop seems like a bit of a pain.
-Eric
Susan Bramhall wrote:
Oh thank you! I was wondering what broke my dev set up. Since we
know the database contains certain tables we could make it
independent with something like "select 1 from up_versions" which is
pretty innocuous.
Susan
Parker Grimes wrote:
Just a quick post regarding the recent fixed issue UP-1771. The
validationQuery="SELECT 1" is invalid SQL in Oracle. You will end
up with "java.sql.SQLException: ORA-00923: FROM keyword not found
where expected"
I fixed it in my uPortal55.xml file by changing that to "SELECT 1
FROM DUAL", but that is Oracle specific. I wonder if it would be
better to define that select string in the rdbm.properties file so
that uPortal55.xml picks it up from there and thus could be changed
per database vendor (since all other connection details are pulled
from there anyway).
Just my thoughts,
Parker
Programmer / Analyst
Southern Utah University
--
You are currently subscribed to [email protected] as:
[EMAIL PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
