RE: [Easysql-interest] ConnectionView Auto Refresh

[John <jo...@to...>]

I think that both are good options. My opinion would be that for
create/drop statements do the auto refresh, perhaps adding an option
some place that would allow that to be turned off. I could look into
adding a configuration panel for EasySQL? Would it be possible to update
in blocks so that the refresh could be optimized? The accelerator would
be useful for instances like the one you mentioned, or generally any
other time you would want to right-click and choose refresh. I hope to
help you with this project if I can, I have the plugin src compiling in
eclipse, but I need to get some of the dependencies set. What do you
think?
 
-JP
 
-----Original Message-----
From: eas...@li...
[mailto:eas...@li...] On Behalf Of
Joseph Toth
Sent: Saturday, November 09, 2002 12:16 PM
To: eas...@li...
Subject: RE: [Easysql-interest] ConnectionView Auto Refresh
 
Select statements return a result set. Update, delete and insert return
number of rows affected. As long as no error message is returned then
your table is created. I could not refresh the list of tables every
time, because if there were a lot of tables in a single database this
would take too long.
There are 2 possible solutions I am thinking of, 
1. Refresh Accelerator - Ctrl+Alt+R
2. Refresh when SQL statement begins with "create".
 
The only slight problem with number 2 is, if you were to create a table
via a statement like "insert into newtable select from oldtable" (which
some DBMSs support) you would have to manually refresh.  Plus number 2
would slow down, when you execute a bunch of create statements at once.
 
Thoughts?
 
Joe
 
-----Original Message-----
From: eas...@li...
[mailto:eas...@li...] On Behalf Of John
Sent: Saturday, November 09, 2002 1:53 AM
To: eas...@li...
Subject: [Easysql-interest] ConnectionView Auto Refresh
 
Any thoughts on having the connection view refresh upon execution of an
SQL statement? I would imagine I am not the only one using Easy SQL to
create tables, and from the best that I can tell the current behavior
doesn't provide any indication of a successful non-select statement. For
instance, a create table command when issued, should refresh the
connection view such that the newly created table is displayed.
 
-JP