Cristopher,
I have had the same problem. Auto-deployment generates loads of parse
errors (ie. bad SQL statements are being fed to the JDBC driver) when I
use PostgreSQL, but not when I use Oracle.
It doesn't seem to stop anything from working, however, as long as you
create the tables yourself. Normally you would want to do that anyway as
far as I can work out.
Does anyone know how to get all container generated SQL statements logged?
--
Thomas Munro <[EMAIL PROTECTED]>
http://www.gi-technology.com/
GI Technology (Paris)
On Fri, 26 May 2000, Christopher Morley wrote:
> I just set up Orion server on Linux and PostgreSQL 7.0 as the backend
> database. When I tried to set up and deploy the sample applications (ATM
> and News), I received the following errors:
>
> **************************************************************
> Auto-deploying news-ejb.jar... SQL error: ERROR: parser: parse error at or
> near ")"
>
> Auto-deploying atm-ejb.jar... SQL error: ERROR: parser: parse error at or
> near ")"
>
> [... several tables are successfully created ...]
>
> Auto-creating table: create table com_acme_atm_ejb_AccountOwner_accounts
> (value
> varchar(255) not null, username_ varchar(255) not null, primary key (value,
> username_))
> Warning: Error creating table: ERROR: Cannot create index:
> 'com_acme_atm_ejb_accountow_pkey' already exists
> **************************************************************
>
> When I subsequently accessed the ATM application and tried to register a new
> user, a SQLException was thrown: "Relation 'com_acme_atm_ejb_accountowner_a'
> does not exist.
>
> Earlier, I set up the same sample applications using HypersonicSQL as the
> backend database and there were no errors at all - with deployment or when
> accessing them.
>
> Do I have something configured incorrectly, or does Orion server have
> inherent problems when paired with PostgreSQL? Also, is there any way to
> turn on some diagnostic logging that will produce more detailed (and useful)
> error messages? I looked through the various logs in Orion's log directory
> and there were no errors at all. The documentation is of very little use
> for troubleshooting. Any help would be greatly appreciated.
>
> Thanks,
> -Christopher Morley
>
>
>
