OCCI and Object Views

Question

Can you use OCCI with object views? Here is the problem that I am seeing:
SCHEMA.SQL:
CREATE TABLE EMP_TABLE
empnumber NUMBER (5),
job VARCHAR2 (20)
CREATE TYPE EMPLOYEE_T as object
empnumber NUMBER (5),
job VARCHAR2 (20) )
CREATE VIEW EMP_VIEW OF EMPLOYEE_T
WITH OBJECT IDENTIFIER (empnumber) AS
SELECT e.empnumber, e.job
FROM EMP_TABLE e
In the code, I try:
env = Environment::createEnvironment(Environment::OBJECT);
conn = env->createConnection(username, password, connection);
RegisterMappings(env);
Employee* e = new(conn,"EMP_VIEW")Employee(); //works
Ref<Employee>e1=new(conn,"EMP_VIEW")Employee(); //fails
Debugging the code, I get an access violation in the Ref constructor:
template <class T>
Ref<T>::Ref(const T *obj)
rimplPtr = new RefImpl((PObject *)obj); // <==Access violation
System specs:
Windows 2000AS
Oracle 9.2.0.4

Answer 1

Sorry to be so long in replying, we decided to move back to objects without the views. Our DBAs were not happy, but sometimes that's how it goes. I did not want to have to go to using associative access for my object manipulation because it is not robust enough for real code, IMHO. So, I would rather do something that I can make work in the real world than have a database model that makes me write what I consider to be bad code. I do wish that OCCI would become more exception-safe as well as I wish that there were not cases where associative access worked but navigational access dod not.
<rant>
One observation about OCCI in general is that using associative access seems to be a bad idea in almost all real-world scenarios. Actually, most of the OCCI constructs seem to be less-than-optimally designed from a C++ perspective. Tossing raw pointers around is not the way toward robust software. And most of the constructs in OCCI do that and worse. None of the high level constructs like Environment, Connection, Statement, etc. are exception safe in any sense of the word. I have (like a lot of you, I'm sure) have had to write a layer on top of the base OCCI classes to enforce some level of exception safety. Not that its a big deal or anything, but just one more thing I would rather not have to do...
</rant>