elaborated QUEST Central for DB2 eight sin

As a engaged Oracle Plsql Development 2 APE-year program, now exits the DB2 Data Warehouse project.

With PL/SQL Developer Reference, below Plsql, elaborated Quest Central for DB2 5.0 n Sin
Execution Platform: Window XP SP3


1: The default number of lines is limited, just start using the time. Let me think that the data is not inserted, because more can not see, also do not suggest that there is actually a lot of other data
At this point the Plsql is the default 10 article. But it's so obvious that you know there's a lot of other data. and can press a toolbar to show all, QC just go to setting change.


2: Long text column display, column width is not adaptive, setting can not choose Unlimited. When the actual data length exceeds the column width. There is no hint that this data is not fully displayed.
I said, you add a ... in the end of the text column. What's also good ah. It also makes me think that inserting data is not normal.
On the Plsql. Text type data can open an edit form to see the full content, date type can also be directly selected to change the date


When the 3:QC result set is displayed, the mouse wheel action is unthinkable. The current focus moves up and down. In all similar forms, the action of the scroll wheel should be scrolling through the contents of the entire form, such as Plsql and Excel, etc.


4: Maybe you will come across the QC SQL form running a piece of code suddenly appear QC program Flash back! Like playing software on Android! Very weird. There is still a problem with the expected compatibility block. And in Plsql


5: In fact, I always think that the biggest drawback of the QC is the program crash recovery mechanism, can say nothing! Used to be a comrade of plsql. The behavior of the code form before resuming it after it crashes must be vividly visible.
This is a very good feature, QC but not, if I encounter problem 4, who will save me write N-day code?


6: What I didn't think of is that QC does not have single step debugging function! It's a bolt from the blue for a developer who has so little demand for development efficiency.

All we can do is to look at the program output parameters and print out the results in the program to do the hard work.
This tool is so weak! Quest Company. You let me say what good.


7: Relative to Plsql. QC is easy to crash and deadlock. For example, if you do big data manipulation in SQL form for a long time without response, the rollback button is no longer working.


8: Angry is DB2 no other useful development tools.

And this QC guy has already stopped updating, and 5.0 is the Terminator.

These are just personal views.

Not to be continued ...

Write it down. I can only say that the use of QC engaged in DB2 development is a very unpleasant thing!

-----------------------------------------

Dylan presents.

Copyright notice: This article blog original articles, blogs, without consent, may not be reproduced.

elaborated QUEST Central for DB2 eight sin