Guillaume:
I installed postgres 8.2.1 on my servers.
When I run the controllers the first time, everything seems to
be OK.
But, when I run the controllers a second time, I get these
outputs:
21:12:17,869 WARN sequoia.controller.recoverylog Backend table BACKEND does
not match database table name case (backend)
21:12:17,869 WARN sequoia.controller.recoverylog Checkpoint table
CHECKPOINT does not match database table name case (checkpoint)
21:12:17,869 WARN sequoia.controller.recoverylog Dump table BACKEND does
not match database table name case (dump)
21:12:17,869 WARN sequoia.controller.recoverylog Log table RECOVERY does
not match database table name case (recovery)
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.
Now, when I run the jpox script to initialize the database, it gives me
these entries
in the distributed request log:
21:14:00,635 cbsweb W 844424930131969 0 CREATE TABLE "DELETEME1168830840549"
(
"UNUSED" int4 NOT NULL
)
21:14:00,764 cbsweb W 844424930131970 0 DROP TABLE "DELETEME1168830840549"
CASCADE
21:14:01,044 cbsweb W 844424930131971 844424930131971 CREATE TABLE "PRODUCT"
(
"SKU" varchar(255) NOT NULL,
PRIMARY KEY ("SKU")
)
21:14:01,714 cbsweb Commit transaction 844424930131971
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?
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Guillaume
Smet
Sent: Friday, January 12, 2007 2:55 AM
To: Sequoia general mailing list
Subject: Re: [Sequoia] Table names are lowercase when using Sequoia from
jpox
Hi Neil,
On 1/12/07, Neil Aggarwal <[EMAIL PROTECTED]> wrote:
> As you can see, the SQL being passed to Sequioa is in uppercase
> letters, why would Sequoia be looking for the same table name
> in lowercase letters?
In the database schema, tables are stored lowercase so it's normal for
Sequoia to look for a lowercase pattern.
IMHO, the problem is that Sequoia is looking for `yourtable` in the
schema and I'm pretty sure that when getting the schema from your
database, Sequoia got yourtable (without the enclosing `) and so
stored yourtable in the schema.
I don't remember if ` is standard per SQL spec but if it is, the
regexps to get the tables from a query should probably be updated to
take it into account.
Thoughts?
--
Guillaume
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
