I'd like to discuss JBIDE-2173 & JBIDE-2162.
>From our JBIDE-2162 discussion:
"I try debug DatabaseMetaData code and seems I find the reason. The main
problem here - for each table extracted all foreing keys for all tables:"
This is of course JBIDE-2173 and it seems here are the problems only with
MySQL - I have check Postrgre and got better performance (Postrgre has no
problems with performance).
Also I try to study the problem to find common workaround for it - and seems
Now to get foreing keys we are using
but it possible to use
and we will get much better performance - I have check it - it possible and
we will get performance O(n) instead of O(n^2) for MySQL.
Seems this have a sense, isn't it?
About JDBCReader - when I try to modify it I saw some potential problem here
This is code to add table into dbs:
Table table = dbs.addTable(quote(getSchemaForModel(schemaName)),
This is code to get table from dbs:
dbs.getTable(schemaName, catalogName, tableName)
obvious that here will be a problem with quotes.
I think the better way incorporate quotes process into DatabaseCollector.
Taking a look at org.jboss.tools.vpe and org.jboss.tools.jsf.vpe.richfaces,
I noticed a cyclic dependency between the two (making the compilation fail).
Obviously trying to remove the dependency from either side gets rid of the
error, but introduces compilation problems since there are imports / code
use from the dependencies.
I was wondering if y'all were aware and had any plans to seperate the code..
the easiest side to fix seems to be org.jboss.tools.vpe, as the only code
dependency is in org.jboss.tools.vpe.editor.util.ElService at line 275:
rst = ComponentUtil.getBundleValue(pageContext, attributeNode);
This is Daily QA report for 31 July 2008.
1 VPE testing.
2 Portlets tests
3 Seam free testing
4 Issues verification
5 New issues found:
Anton Klimkovich mailto:firstname.lastname@example.org