Hi Neil,
On 1/15/07, Neil Aggarwal <[EMAIL PROTECTED]> wrote:
Looking at the backend database, it has the tables with lower case even
though my
virtualdatabase config has them in upper case.
Considering they are just warnings, I decided to move on.
I have the same problem and probably every person running sequoia. I
don't understand why the recovery log tables and columns are
uppercased in the default configuration file.
I checked this problem a long time ago and IIRC there's barely any
chance the case matches between the configuration file and the results
in the database.
Emmanuel, what's your opinion about this?
"SKU" varchar(255) NOT NULL,
PRIMARY KEY ("SKU")
)
The good news is that JPOX is SQL compliant when the database also is :).
The cluster log has this output:
2007-01-14 21:14:00,765 WARN backend.DatabaseBackend.cbsweb2 Unable to find
table "deleteme1168830840549" in database schema, scheduling query DROP
TABLE "DELETEME1168830840549" CASCA... in conflicting queue. Method:
getQueueAndWriteLockTables
It looks like the table case is still a problem.
Looking at the backend database, the deleteme table is not there anymore so
it looks like
it executed.
Why would it put the query in the conflicting queue?
I have to take my train this morning. I'll take a look at this problem
during the trip. It seems that there's a problem in the DROP TABLE
regexp. I'm not sure I'll be able to connect me for the next two days
but I'll be back for sure on tuesday evening.
--
Guillaume
_______________________________________________
Sequoia mailing list
Sequoia@lists.forge.continuent.org
https://forge.continuent.org/mailman/listinfo/sequoia
