dbVis becomes unstable after deleting rows from one of the result tabs
a
anonymous
started a topic
over 12 years ago
[This topic is migrated from our old forums. The original author name has been removed]
Here is the scenario:
SQL window contains:
select * from table where .....
select * from another_table where .....
You execute this , dbvid returns *2* result tabs. +(Interestingly, only 1st one is editable and second one is not. ?? )+
You click to select all rows from the result grid and click on Delete button.
The error is shown below. The app becomes unresponsive, but (fortunately) lets you save any unsaved work, although does not react to keystrokes.... Whats more, the rows DO get deleted....
{color:#800000}An error occurred while executing the database request for:
Adaptive Server Enterprise
Adaptive Server Enterprise/15.5/EBF 18661 SMP ESD#4/P/x86_64/Enterprise Linux/asear155/2545/64-bit/FBO/Thu Jun 16 06:45:54 2011
jConnect (TM) for JDBC (TM)
jConnect (TM) for JDBC(TM)/7.07 GA(Build 26686)/P/EBF19793/JDK 1.6.0/jdbcmain/Tue Dec 20 04:39:14 PST 2011{color}
{color:#800000}Short message:
An error occurred while performing the operation:
Cannot re-execute since this result set was produced as one of several result sets in a multi statement operation (typically a stored procedure generating several results).{color}
{color:#800000}System Information:
Product: DbVisualizer Personal 8.0.9
Build: #1751 (2012/04/30 11:38)
Java VM: Java HotSpot(TM) Client VM
Java Version: 1.6.0_30
Java Vendor: Sun Microsystems Inc.
OS Name: Windows XP
OS Arch: x86
OS Version: 5.1{color}
Re: dbVis becomes unstable after deleting rows from one of the result tabs
Hi Alex,
Can you please share some more details about the actual tables such as the CREATE TABLE DDL for each?
How much data are in them when you Select All rows and then delete the content?
Regards
Roger
a
anonymous
said
over 12 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: dbVis becomes unstable after deleting rows from one of the result tabs
Sure:
*Table1 -- 54 rows*
go
create table Table 1
( APP_ID varchar(10) not null,
FunctionName varchar(32) not null,
--- varchars
P1 varchar(255) null,
P2 varchar(255) null,
P3 varchar(255) null,
P4 varchar(500) null,
--- int
N1 int null,
N2 int null,
N3 int null,
-- big varchar
V1 varchar(520) null,
-- floats
D1 float null,
D2 float null,
D3 float null,
Description varchar(50) null
constraint FK_func_prm foreign key (APP_ID)
references Table2 (APP_ID)
)
lock datapages
go
create unique clustered index idx0
on Table1 (APP_ID, FunctionName)
*Table 2: -- 8 rows*
go
create table Table2
( APP_ID varchar(10) not null,
AppName varchar(64) not null,
Comment varchar(64) null,
CreDte datetime not null
)
lock allpages
go
create unique clustered index idx0
on Table2 (APP_ID)
go
Keep in mind, the two selects that I mentioned in my original post have a 'where APP_ID = ' constraint ..
Roger Bjärevall
said
over 12 years ago
[This reply is migrated from our old forums.]
Re: dbVis becomes unstable after deleting rows from one of the result tabs
Hi Alex,
I've tried this now and for me both result sets are editable and the delete/save is fast and produce no errors.
Can you please enable debug of DbVisualizer and then run the two queries.
Then perform the delete/save.
Post or email the debug output.
Regards
Roger
support@dbvis.com
a
anonymous
said
over 12 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: dbVis becomes unstable after deleting rows from one of the result tabs
Re: dbVis becomes unstable after deleting rows from one of the result tabs
Hi Alex,
The problem seem to be that you are running the SELECTs as a single statement (no separator between them):
SELECT * FROM dbo.Table1 where APP_ID = '2'
SELECT * FROM dbo.Table2 where APP_ID = '1'
This is processed by the Sybase server and two result sets are fetched by DbVisualizer. Due to parsing and that DbVisualizer don't support this syntax, it can only determine that the first result set is editable while the other isn't.
Then when you edit the first result set and press Save the edits are in saved but DbVisualizer cannot reload that specific result set since it is originally created by the compound SELECT statement.
I will register a ticket so that none of the result sets will be editable if passing multiple SQLs in a single statement.
I suggest you put a "go" between the two statements in order to workaround this issue.
Regards
Roger
a
anonymous
said
over 12 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: dbVis becomes unstable after deleting rows from one of the result tabs
Sounds good. Thank you
Roger Bjärevall
said
over 8 years ago
[This reply is migrated from our old forums.]
Re: dbVis becomes unstable after deleting rows from one of the result tabs
Hi Alex,
Sorry for not informing about this earlier but this is fixed in 9.2.11 and later versions.
Regards
Roger
anonymous