11.3 SDK Feature Support

Compare feature support and API entry points to choose an SDK for your application. See each SDK page for installation, connections, functions, and runnable examples.

If choosing an SDK for the first time, read Choose an Integration Method first, then use this page to compare required features and exact API paths.

Nullable Metadata

Machbase reports SELECT result column nullability as NO_NULLS, NULLABLE, or UNKNOWN. Applications must handle NULL for both NULLABLE and UNKNOWN.

Expressions, aggregates, VIEWs, and JOIN results may report UNKNOWN. Do not equate a source column schema constraint with query result metadata.

PRIMARY KEY Metadata

Expressions, aggregates, and the NULL-supplying side of an outer join may not preserve the source column primary key attribute.

ROWID from INSERT

In Machbase 8.7.0 Standard Edition, a successful single INSERT ... VALUES can provide a ROWID to supported SDKs.

Batches, executemany(), Append, loaders, INSERT ... SELECT, and UPSERT do not return a single ROWID. See ROWID for SQL semantics and table-specific constraints.

Append APIs and Table Types

Keep ordinary query connections and Append handle lifecycles distinct, and check close and flush results. O indicates support verified in the cited source/tests. △ means only a generic path is available and further table-specific regression testing is needed. Append extensions are not standard ODBC or database/sql features.

ARRAY and Selected-Column Append

Machbase DBMS 8.7.0 ARRAY support is as follows:

Use a Machbase DBMS 8.7.0 server with an SDK build that includes ARRAY support. SQL ARRAY element positions and Machbase-specific SDK positions are 0-based. Existing full-row scalar Append APIs are unchanged. The Node.js prepared fallback also supports SparseArray. Go requires v2 main source after neo-client PR #17; until a public v2 release is specified, do not assume a published module version provides support. See Sparse ARRAY and Selected-Column Append API for input methods and APIs.

AUTH KEY

See AUTH KEY Authentication for key generation, registration, and rotation. See supported SDK pages for connection options.

Transactions, Prepare, and Binding

Prepared statements and parameter binding are separate from transaction support. See Named Bind Parameter for placeholder syntax.

For TAG data UPDATE in Machbase 8.7.0 Standard Edition, existing positional/named SDK APIs can bind NAME and BASETIME predicate values. NFX #4127 regression tests cover C/C++ SQLCLI, Go database/sql, JDBC, Node.js, Python, and .NET. ODBC is not included in that SDK regression matrix; it binds ? or named SQL placeholders by ordinal through standard SQLBindParameter(). See TAG Data UPDATE Binding for predicate requirements.

△ in the Transaction column means executing transaction SQL on the same connection instead of using a dedicated object. △ in Named bind means a driver extension or a client path that converts values to SQL literals, rather than a standard named binding API.

Verified Versions and Provenance

Some Node features in NFX cce422d were added after the public npm 1.0.1 release. Do not assume feature parity from the registry package version string. Check the artifact commit provenance or use an NFX source build.

ARRAY and selected-column Append were verified against NFX 655d1333870313c4951698b89c9a3c9ada11d630 and merge commit f756986c4836982723e2aa7727ec05b7e05e9707. Use Machbase DBMS 8.7.0 as the server baseline and verified SDK artifacts containing those changes as the client baseline.

SDK References