Restrictions

The is subject to the following restrictions:
  • The Object Interface for C++ does not support object persistence for application classes; it does not automatically map instances of database tables to application classes or vice versa.
  • You cannot directly update the database data by modifying the corresponding value objects; to modify the database data that corresponds to the data returned to client programs in value objects, you must issue SQL queries, or the methods ITCursor::UpdateCurrent() and ITCursor::DeleteCurrent().
  • You cannot develop server functions by using the Object Interface for C++.
  • Do not mix database access through the Object Interface for C++ and lower-level interfaces (like the DataBlade® API) in the same application.
  • The Object Interface for C++ is not thread-safe. Do not use Object Interface for C++ in multi-threaded applications or environments.