StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16186942
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-24T08:21:20.043
FavoriteCount
0
LastActivityDate
2013-04-24T08:21:20.043
LastEditDate
LastEditorUserId
0
OwnerUserId
2314464
ParentId
15952590
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Assuming you are actually connecting to the same database this is caused by not committing the <code>INSERT</code> in the sql*plus connection. Oracle by default does not run in auto-commit mode when connecting via OCI (which sql*plus uses to connect). Any <a href="https://en.wikipedia.org/wiki/Data_Manipulation_Language" rel="nofollow">DML</a>(<code>INSERT ...</code>) executed in sql*plus will not be visible to any other session until it is committed. This is because Oracle provides a <a href="https://en.wikipedia.org/wiki/Isolation_%28database_systems%29#Read_committed" rel="nofollow">read committed</a> isolation level by default. The only thing visible to other users across sessions are write locks. It doesn't matter if you connect the second connection via JDBC or OCI, it won't see the changes till you commit the first connection. <hr> To test this out try opening 2 sql*plus connections and run the following: <pre><code>-- Executing DDL in Oracle causes an implicit commit before and after the -- command so the second connection will see the existence of this table: CREATE TABLE foobar ( x VARCHAR(1) ); </code></pre> Execute this in connection #1 - you should get zero (we haven't inserted anything yet): <pre><code>SELECT COUNT(*) FROM foobar; </code></pre> Execute this in connection #2: <pre><code>INSERT INTO foobar ( x ) VALUES ( 'A' ); </code></pre> Execute this in connection #1 - you should still get zero (<code>INSERT</code> is not committed so connection #1 cannot see it): <pre><code>SELECT COUNT(*) FROM foobar; </code></pre> Execute this in connection #2: <pre><code>COMMIT; </code></pre> Execute this in connection #1 - you should get 1 (it's committed now): <pre><code>SELECT COUNT(*) FROM foobar; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POdifferent results from query in java code and on oracle db server: but no connection error
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsehrope
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.