Multi line select statement rollback issue

Hi,
I have a bug, at least I hope it's a bug and not a feature.

I have several select statements (with the intention of updating select values) in a sql window and run them all simultaneously.
Each opens up in a separate tab as expected.
I unlock the first tab and make the change. I click the tick to 'post' the change but hold off from committing.
I then move onto the second tab and do the same.
And so on.
Finally I commit.
I then rerun the initial selects and get the various tabs of data.
At this point only the last result set's changes had been affected, all the others seemingly rolled back/undone.

Anybody else noticed this? Am I being dumb?

FYI, i'm running on a Virtual machine on top of linux; here's the support info :

PL/SQL Developer
Version 10.0.2.1697
01.85318 - 5 user license
Windows 7 (64-bit) 6.1 Build 7601 (Service Pack 1)

Physical memory : 2,096,696 kB (813,884 available)
Paging file : 4,193,392 kB (2,811,120 available)
Virtual memory : 2,097,024 kB (1,796,708 available)

Parameters
C:\Program Files (x86)\PLSQL Developer\plsqldev.exe

Preferences
Session mode: Multi
OCI Library:
Use OCI7: False
Allow Multiple Connections: True

Preference Files
C:\Program Files (x86)\PLSQL Developer\Preferences\Default\Default.ini
C:\Users\me\AppData\Roaming\PLSQL Developer\Preferences\me\default.ini

Plug-Ins
*Active Query Builder (C:\Program Files (x86)\PLSQL Developer\PlugIns\ActiveQueryBuilder.dll)
(* is Active)

Aliases
ORA10GR1

Homes

DLLs
c:\oracle\instantclient\oci.dll

TNS File
c:\oracle\LocalConfig\tnsnames.ora

Using
Home:
DLL: c:\oracle\instantclient\oci.dll
OCI: version 11.1
Oracle Database 10g Release 10.1.0.2.0

Character Sets
Character size: 1 byte(s)
CharSetID: 1
NCharSetID: 2000
Unicode Support: True
NLS_LANG:
NLS_NCHAR_CHARACTERSET: AL16UTF16
NLS_CHARACTERSET: US7ASCII

Thanks.
 
I cannot reproduce this. I tried the following script:

Code:
select d.*, rowid from dept d;
select e.*, rowid from emp e;

I modified a dept record and posted the changes without committing. Next I modified an emp record and posted the changes. After pressing the commit button and re-executing the queries, all changes are there.

Can you verify this scenario?
 
Hmmm....
A bit of a delay on my part.
I've just tested again and it seems to work as expected now.
Makes me look like i'm going mad but it really was doing as described.
Because it was so odd I had colleagues come to check that I wasn't doing anything stupid before I posted to question it.

Thanks for the reply though.
 
Back
Top