Paul,
I finally realized that the problem apparently came from a bad
parameter setting on my part. I had left "<DatabaseSchema
schemaName="public"/>". Removing it fixed the problem. Strangely,
though, the "mytable" table used in my example was created in the
"public" schema. My understanding of the "DatabaseSchema" parameter is
that it still should of been able to recognize the table. Anyway,
removing altogether the parameter was the solution for my case and now
the Sequoia console works perfectly well. Sorry for the inconvenience.
Yes, it should.
When we call getTables on your database driver we either give null to
fetch all schemas or the schema name that you provide. For some reason,
your driver did not return any table (or at least not 'mytable') when
'public' was given in the schema name. That may be a JDBC driver bug.
Note that sometimes case sensitivity is an issue with some drivers.
Thanks for the feedback,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
