Hi Randy,
Thanks for the reply ! Tried those changes, but still getting the same
problem ... I noticed a few other tables with column name "value". Is it
that _all_ of those were changed to column_value ? :-(
----Original Message Follows----
From: "Scott T Weaver" <[EMAIL PROTECTED]>
Reply-To: "Jetspeed Users List" <[email protected]>
To: "'Jetspeed Users List'" <[email protected]>
Subject: RE: J2 - Any DB Changes since M3 ?
Date: Thu, 10 Nov 2005 09:58:14 -0500
Hi Amit,
I was just fixing those myself as I am upgrading our deployment servers to
M4. Here are the tables that need to change from "VALUE" to "COLUMN_VALUE"
Affected Tables:
PA_METADATA_FIELDS
RULE_CRITERION
SECURITY_CREDENTIAL
HTH,
-Scott
> -----Original Message-----
> From: Shah Amit [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 10, 2005 9:50 AM
> To: [email protected]
> Subject: J2 - Any DB Changes since M3 ?
>
> Hi all,
>
> Just wondering if there were any DB changes since M3 in the latest
> jetspeed
> in svn head ... I am trying to run new jetspeed against the M3 db, but
> getting some a0.column_value not found exception ...
>
> Any suggestions ? I can't just drop my DB and flush it with new one
> because
> I have tons of other stuff created on that DB :-(
>
> Thanks,
> Amit
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
