How to open multiple sessions for one user?

Question

Sorry for the silly question but I couldn't find it googling or searching through this forum, so I started wondering whether it's possible in SQL Developer to open multiple sessions for one user. I'm fairly new to SQL Developer and databases in general.
When I open SQL Developer and connect to a schema, a worksheet opens named MYSCHEMA. If I disconnect then connect, another worksheet opens, named MYSCHEMA~1. I assumed these were different sessions, but if I enter into one worksheet:
select col1 from my_table where row_id = 1
-- shows result is 1
update my_table set col1 = 0 where row_id = 1
select col1 from my_table where row_id = 1
-- shows result is 0and then enter into the second worksheet:
select col1 from my_table where row_id = 1
-- shows result is 0I would have expected the second worksheet to report 1 because the first worksheet did not issue a COMMIT. Thus, I'd guess both worksheets are the same session? Is that right? If so, how do I have two sessions open simultaneously (opened by same user)?
I'm trying to implement the code at the bottom of this post, for which testing requires at least two sessions:
Re: Help with Procedure
Edited by: tem on Apr 18, 2012 6:44 AM

Answer 1

Thanks Jim,
Ctrl-Shift-N doesn't do anything for me. I'm on a mac -- by experimenting it looks like command-N does what you're looking for. This appears to be the same as left-clicking on the "New" icon in the top left corner of SQL Developer, or selecting from the pull-down menu, File > New.
This opens "Create a New" window that appears to be a wizard. What would I select at this point? Options are: Database Connection, Table, View, Package, ...
I don't see an option for "Worksheet".
UPDATE:
OK, I found that if I select "SQL File", a worksheet becomes available. Perhaps this is what you intended. However, when I issue the command
select col1 from my_table where row_id = 1;it still returns 0 instead of 1. Hmm, maybe my initial assumption was wrong -- if this is a second (e.g. different) session, should I expect the changes made in the first session in SQL Developer (the UPDATE command) WITHOUT a commit, to be observed in this second session? I thought that changes made in one session were not viewable in a different session until these changes are committed in the first session? If so, how to show this in SQL Developer? I must be missing something basic here.
Or, is SQL Developer issuing some sort of "auto-commit" without my knowledge?
Edited by: tem on Apr 18, 2012 8:00 AM