Trying to understand Oracle, ODBC, SQL*NET interface
From: CS <chagood_at_geocities.com>
Date: 1997/12/01
Message-ID: <01bcfdee$427774e0$839790cc_at_carla>#1/1
Date: 1997/12/01
Message-ID: <01bcfdee$427774e0$839790cc_at_carla>#1/1
- Is ODBC married to text? Do you have to provide a text string (SQL syntax) to ODBC interfaces?
- Can you provide a binary value in an ODBC call?
- How do you do bulk loading using ODBC? Is there a concept of a transaction? Is there a way to eliminate/turnoff transactions for large loading?
- What API interfaces exist to Oracle from a remote NT platform machine? What does SQLNet buy you?
- Do you have to have SQLNet to run and ODBC interface from a remote NT workstation and access an Oracel database?
- What communications mechanisms does SQLNet support? Can you direct it to use shared memory orTCP/IP sockets to interact? Are there any differences in the interface if running the same task on the local machine vs. on a remote machine?
- Is there a C interface to SQLNet that allows insert and update calls to use binary values for fields? From a remote machine?
- How do you do bulk load binary data (double precision IEEE floating format) with a program to an Oracle Database. Does not want to convert data to string due to lost of precision and overhead (In our application it does matter). Data will have mathematically