OCILIB Next Release features
News August 9th, 2008I’m currently working on a list of new features for the next release of OCILIB.
Initially, I was focused on extending object API support, thread contextual error handing and Events support.
OCILIB already has some support for objects but not for collections and references.
Implementing theses features is a lot of work and i’ll reserve it for the branch version v3.x.
So, for branch v2.x, at the moment, i’m thinking to focus on :
- Session Pools (>=10g)
- Events (>=8i)
- Implicit fetch of rowid (>=11g)
- Statement cache (=>9i)
- Scrollable cursors (>= 9i)
- Lob tuning (prefetch size, chunck size, internal array allocation) (>=11g)
If you have any comments, ideas for OCILIB new functionalities, just let me know !
August 21st, 2008 at 5:27 pm
A function returning the status of a statement (ie returning the detailed status of OCIStmtExecute) would be quite useful, especially to know if a select returned data or not.
Something like OCI_StmtStatus( OCI_Statement * Stmt) than would do:
return Stmt->con->status;
August 23rd, 2008 at 7:41 pm
I’m afraid that’ not possible before a fetch call.
Only a fetch call can tell if some data is available.
The internal return code of OCIStmtExecute() cannot indicate if some data is available from a select statement.
September 12th, 2008 at 11:30 am
Hello,
First things first ;)! I want to tell you GREAT JIOB with this library. Respect!
I myself struggled with OCI for some time and was on my way to create something like that, but you beat me up :).
And now:
I couldn’t find an option to retrieve an error position inside SQL. Unless I just missed that in your docs.
In the original OCI there is such possibility, I just didnt find it in your lib.
Could you, pls, add that feature?
September 12th, 2008 at 12:02 pm
Hi z95_hunter,
Yes, it will be added to v3.0.0….
I just need to handle the attribute OCI_ATTR_PARSE_ERROR_OFFSET when a parse call failed.
So, I’ll add a public function OCI_GetSqlErrorPos(OCI_Statement *stmt);