Options for opaque data types
Opaque data types are ultimately defined as C structures; when you create an opaque data type with BladeSmith, the built-in data types you can choose as members are C structures provided by the DataBlade® API. However, you can implement opaque data types as value objects in other external languages. A value object is a self-contained binary object that provides standard interfaces to its users. Value objects can be used in client applications.
You create client value objects in BladeSmith by specifying an optional client implementation of your opaque data type, in addition to the mandatory server implementation. For a complete list of options you have when you create an opaque data type with BladeSmith, see Opaque data type.
When you decide what functionality and which language or languages
to use for your opaque data types, consider the following options:
- Whether to create client value objects in addition to opaque data types for the database server. See ActiveX value objects for more information.
- Which language to use for your opaque data types. See Limitations of opaque types for each language for more information.
- Whether to use different languages for the server and client implementations. See Combined languages in server and client implementations for more information.
- Whether to embed opaque data types as members of other opaque data types. See Embed opaque data types within opaque data types for more information.