Start a new topic

Problems using Query Builder

[This topic is migrated from our old forums. The original author name has been removed]

Hi, We just started evaluating the DBVisualizer Personal version this week, specially the Query Builder feature. We are looking for a database query tool to be used by non technical people and DBVisualizer is in our top list, because of this Query Builder feature. We are testing the 5.1.1 version on Windows XP. But we found the following issue when playing with it: When trying to build the where clause through the Conditions option on the query builder, we've noticed the application seems to freeze for several seconds, then after a while everything looks normal again. It looks like, from our perception, this waiting time depends on the number of records the table presents. We've tried with different sets of databases (Oracle, Informix, MySql) and the same behavior occurred. More specifically, the problem happens when we click on the "1.1" button, then select the table name, then select one field. That's when the freezing (or waiting time) occurs. This time will be proportional to the number of records on the particular selected table. This just happens the first time the table is included. After that any other operation runs smoothly. Also, when removing one table from the query builder grid the conditions related to this table are not automatically removed, in which case it requires us to manually remove them. So, is there any option where those conditions are removed whenever the associated table is removed from the grid? Thanks, and let me know if more information is needed. Jose Lima Lead developer Sabre Holdings.

[This reply is migrated from our old forums.]

Re: Problems using Query Builder
Hi Jose, Thanks for the feedback, we appreciate it. The waiting time you see when using the table/column menu in a condition field for the first time for a particular table is most likely the time it takes to get the column names for the table from the database. As you have noticed, the more columns the table has, the longer it takes. We will look into ways to get the column names in a different way to solve this problem. We will also look into automatically removing all conditions related to a table when the table is removed. Thanks again for your feedback, Hans
[This reply is migrated from our old forums. The original author name has been removed]

Re: Problems using Query Builder
Thank you for you prompt response. As long we continued evaluating the tool, we observed this other behavior: Is there a way of saving the Query Builder graphical Model ? On the SQL Editor we can save the current context, but when we re-opened later it does not recreate the graphical model. Thanks, Jose Lima
[This reply is migrated from our old forums.]

Re: Problems using Query Builder
Jose, It is currently not possible to save the model. We will add a reverse engineering capability which lets you load a SQL statement into the Query Builder and it will setup the diagram, joins, conditions, sorts, etc. The reverse engineering feature is planned for the 5.2 version (Q1 2007). Regards Roger