Skip to main content

SOCI was initially developed in the environment where Oracle was the main database technology in use. As a wrapper for the native OCI API (Oracle Call Interface), the name 'Simple Oracle Call Interface' was quite obvious - until the 2.0 release, when the internal architecture was largely redesigned to allow the use of backends that support other database servers. We have kept the same name to indicate that Oracle is the main supported technology in the sense that the library includes only those features that were naturally implemented in Oracle. With the 2.1 release of the library, two new backends were added (MySQL and SQLite3) and we decided to drop the original full name so that new users looking for a library supporting any of these simpler libraries are not discouraged by seeing 'Oracle' somewhere in the name. The other possible interpretation was 'Syntax Oriented Call Interface', which stresses the fact that SOCI was built to support the most natural and easy interface for the user that is similar to the Embedded SQL concept (see below). But on the other hand, SOCI also provides other features (like object-relational mapping) and as a whole it is not just 'emulator' of the Embedded SQL. With all these considerations in mind, SOCI is just 'SOCI - The C++ Database Access Library'.

Total Downloads
5.6K
5,602
Published
Apr 7, 2014
Latest stable version

Install

.NET CLI
dotnet add package soci --version 3.2.0
Package Manager Console
Install-Package soci -Version 3.2.0
PackageReference
<PackageReference Include="soci" Version="3.2.0" />

Frameworks

No framework metadata available.

Dependencies

[3.2.0, )

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.