On Mon, 14 Jan 2008 14:30:30 +0100, Thomas Mortagne wrote
No as the goal of this code is not to chose the database/schema where to works, it set the schema name to use when generating the update script for database engines based on schemas. MySQL does not need it because MySQL is based on databases.
What means 'based on schema/based on database' ? I. e. what is the difference from the API point of view ? (Or this difference is hided by hibernate ?)
The only place where database/schema is really changed is setDatabase() and only in non virtual mode as far as I know.
You again talk about 'logical' layer. Idea is do not touch 'logical layer' at all, instead touch hibernate configuration. As I understand, table.setScheme() do this for 'scheme-based' databases (?) And must exist some other way for mysql [?] (so, I go to read hibernate docs).
2008/1/14, rssh <rssh@gradsoft.com.ua>:
No, it's work for me. (may be because of calls to table.setSchema() in updateSchema(), which called first)
table.setSchema() is never called with mysql... I will make a some real test when I have time before continue to complain :)
May be better add mysql here ? (i.e. call setSchema for any database).
-- Ruslan Shevchenko GradSoft. http://www.gradsoft.ua
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Ruslan Shevchenko GradSoft. http://www.gradsoft.ua
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Ruslan Shevchenko GradSoft. http://www.gradsoft.ua