Hi Jonathan,
I am running 2.10.10. I just double-checked. Is there any way to
disable the parsing? Can I just pass the SQL straight-through?
If you disable the ResultCache, the parsing for Select queries should
not be needed. The parsing is required to order write queries properly.
When we fetch the database schema, we ask the database for all schema
names and try to prepend them to the table names to make sure that we
can have both fully qualified and short table names.
Have you checked if the parsing was case sensitive? The info might be
there but with the wrong case?
If you turn debugging on in log4j.properties, you should be able to see
what schema is fetched from the backends at 'enable' time.
Thanks for the feedback,
Emmanuel
*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On Behalf Of
*Robert Hodges
*Sent:* Sunday, July 20, 2008 2:18 AM
*To:* Sequoia general mailing list
*Subject:* Re: [Sequoia] Question about unknown table error
Hi Jonathan,
It looks as if Sequoia is incorrectly parsing the schema name. What
version of Sequoia are you running? If you are not on 2.10.10 please
upgrade. There was at least one bug in this area that was fixed recently
Thanks, Robert
P.s., I’m on vacation so with luck others on the list can help you
further.
On 7/18/08 7:36 PM, "Jonathan Stockho" <[EMAIL PROTECTED]> wrote:
I recently got Sequoia for my project at work and have a problem that
I can’t seem to figure out.
In my Java code, the queries to my database use schema name as part of
the table name. In other words, if my database had a schema named
“SCHEMA” and a table named “TABLE”, I might have a query such as:
SELECT * FROM SCHEMA.TABLE;
This works with my existing JDBC driver.
When using Sequoia I get the following error:
Error during command execution (Unknown table ‘SCHEMA.TABLE’ in this
SELECT statement: ‘SELECT * FROM SCHEMA.TABLE’).
If I try to use “SELECT * FROM TABLE;” that works, but if I happen to
have more than one schema (which happens during testing) I can’t
ensure which TABLE is being queried.
I am using a Derby database. In my experience, I have always been able
to attach the schema name to the table name for queries, and I thought
this was standard SQL. Any idea why this won’t work with Sequoia? I
can remove the schema part from the name, but would prefer to leave it
as it is used to ensure the query comes from the right table.
Any help would be greatly appreciated.
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
