JBIDE-2173 & JBIDE-2162 - performance improvement (for MySQL?)
by Vitali Yemialyanchyk
Max, hi.
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
it exist!
Now to get foreing keys we are using
getMetaDataDialect().getExportedKeys
but it possible to use
getMetaDataDialect().getImportedKeys
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)),
getCatalogForModel(catalogName), quote(tableName));
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.
Best regards,
Vitali
16 years, 3 months
QA Daily report 30 June 2008.
by Anton Klimkovich
This is Daily QA report for 30 June 2008.
1. Free testing of JBT 2.1.2 latest avilable build.
2. Free testing of JBT 3.0 alpha.
3. Testcases creation for pages.xml.
4. Issues found:
Component/s: Visual Page Editor
http://jira.jboss.com/jira/browse/JBIDE-2464
--
Best regards,
Anton Klimkovich mailto:aklimkovich@exadel.com
16 years, 4 months
Re: Issues in 2.1.2.GA Build
by John Graham
Marshall,
2417
2416
2415
are not for the 2.1.2 GA build -- these are for a later release.
-- John
On Fri, 2008-06-27 at 14:02 -0500, Marshall wrote:
> I've seen a few new JIRAs popup from the 2.1.2.GA build, and made a
> list of JIRAs that are marked as Major so I can keep track of the
> release-stoppers.
>
> Denis & QA:
>
> - Is it correct to assume all of these issues are stoppers until
> release?
> - If not, can you mark them correctly as Minor so we can focus on
> getting the "Major" JIRAs fixed?
>
> Here's a link to the list I'm looking at:
> http://tinyurl.com/6yrybe
>
16 years, 5 months
