StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1075812
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-07-02T17:57:50.227
FavoriteCount
0
LastActivityDate
2009-07-02T17:57:50.227
LastEditDate
LastEditorUserId
0
OwnerUserId
105929
ParentId
1074289
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
In the configuration you described you will use both 'drivers'. Technically, System.Data.Odbc is not a driver, is a <a href="http://msdn.microsoft.com/en-us/library/ms810268.aspx" rel="nofollow noreferrer">provider</a>. To understand what's going on you need to separate the managed side (.Net) from the native side (ODBC). The Microsoft ODBC Driver for Oracle is a driver for ODBC. It allows any application capable of ODBC to connect to Oracle. ODBC is a native technology. On the otehr hand .Net Framwork uses managed data provider for it's data access. One such provider is the System.Data.Odbc provider which allows .Net applications to connect to any ODBC data source. So when your managed application connects to maConenctionString it uses the System.Data.Odbc provider to connect to the ODBC source named 'oracle' and the ODBC manager will load the Microsoft ODBC Driver for Oracle to connect to the actual back end. Now that being said <a href="http://msdn.microsoft.com/en-us/library/ms973871.aspx" rel="nofollow noreferrer">it is recommended you use native providers whenever possible</a>. So instead of connecting via the ODBC provider to an ODBC data source, is much better if you use directly the respective native provider like the <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=4F55D429-17DC-45EA-BFB3-076D1C052524&displaylang=en" rel="nofollow noreferrer">.Net Managed Provider for Oracle</a> (for older frameworks) or the newer <a href="http://msdn.microsoft.com/en-us/library/system.data.oracleclient.oracleconnection(VS.80).aspx" rel="nofollow noreferrer">System.Data.OracleClient</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWindows ODBC Datasources and .Net System.Data.Odbc: Which driver is used?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRemus Rusanu
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWindows ODBC Datasources and .Net System.Data.Odbc: Which driver is used?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.