FairCom DB

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

FairCom DB is FairCom Corporation's flagship database product. It is optimized for high-speed transaction processing of JSON documents and binary records.

Application Programming Interface (API) is a type of software interface that provides a service to other software. 

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

FairCom DB is FairCom Corporation's flagship database product. It is optimized for high-speed transaction processing of JSON documents and binary records.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

A database table defines a specific type of record, such as a person's data. A table contains zero or more records. A record contains two or more fields.

In the JSON DB API, a table must always have an "id" field to uniquely identify each record. A table is similar to a collection in a NoSQL database.

A FairCom table may have up to 2500 fields and zero or more of those fields may have a JSON type.  Each field (or group of fields) may be indexed by one or more indexes with a maximum of 500 indexed fields. One or more individual properties inside a JSON field may also be indexed.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

INTEGER is a FairCom database field type containing a signed integer number, such as -2147483648. It is stored in a record as a signed 32-bit integer number with a range from -2,147,483,648 to 2,147,483,647.

VARCHAR is a FairCom database field type containing a variable-length string, such as "my string". It is stored in a record as a variable-length sequence of UTF-8 characters with user-specified maximum length up to 65,500 bytes.

LVARBINARY is a FairCom database field type containing a variable-length binary value. It is stored as a variable-length sequence of bytes up to 2 Gigabytes in length. Each LVARBINARY field in each record includes a four-byte length header.

BIT is a FairCom database field type containing a Boolean value of 0 or 1. It is stored in a record as an 8-bit integer.

DATE is a FairCom database field type containing a date value, such as "2022-03-08". It is stored in a record as an unsigned 32-bit integer that represents a specific day in the Gregorian calendar. A date has three parts: year, month, and day. It does not include time or a timezone offset.

TIME is a FairCom database field type containing a time value, such as "15:35:02:00". It is stored in a record as a 32-bit unsigned integer that represents a specific millisecond in a day. A time has four parts: hour, minute, second, and millisecond which represent the number of milliseconds after midnight. It does not include a date or a timezone offset.

TIMESTAMP is a FairCom database field type. It is stored in a record as a 64-bit number that represents a specific DATE and TIME. It does not include a timezone offset.

JSON consists of one or more JSON values that can be nested inside each other.

Each value is one of the data types: JSON object, JSON array, JSON string, JSON number, JSON Boolean, or JSON null.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

REAL is a FairCom database field type containing a signed floating point number, such as -34028234.664 or 1.1754943508e-38. It is stored in a record as a 4-byte, IEEE 754 , binary floating point number. It provides 6 to 9 decimal digits of approximate precision. In contrast, DOUBLE provides 15 to 19 digits of approximate precision. REAL also supports infinity, -infinity, and NaN.

DOUBLE is a FairCom database field type containing a signed floating point number, such as -179769313.48623158 or 2.2250738585072014e-308. It is stored in a record as an 8-byte, IEEE 754 , binary floating point number. It supports a wide range of numbers and its calculations are fast. It provides 15 to 19 digits of approximate precision. It supports infinity, -infinity, and NaN.

TINYINT is a FairCom database field type containing a signed integer number, such as -128. It is stored in a record as a signed 8-bit integer number with a range from -128 to 127.

SMALLINT is a FairCom database field type containing a signed integer number, such as -32768. It is stored in a record as a signed 16-bit integer number with a range from -32,768 to 32,767.

INTEGER is a FairCom database field type containing a signed integer number, such as -2147483648. It is stored in a record as a signed 32-bit integer number with a range from -2,147,483,648 to 2,147,483,647.

BIGINT is a FairCom database field type containing a signed integer number, such as -9223372036854770000. It is stored in a record as a signed 64-bit integer number with a range from -9,223,372,036,854,770,000 to 9,223,372,036,854,770,000.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

MONEY is a FairCom database field type containing a signed decimal number, such as -12345678900.0001. It is stored in a record as a signed, fixed-point decimal number with 32 digits of precision. It consumes 19 bytes of storage. The "scale" property specifies 2 or 4 digits to the right of the decimal point. The remainder of the precision is to the left of the decimal point.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

REAL is a FairCom database field type containing a signed floating point number, such as -34028234.664 or 1.1754943508e-38. It is stored in a record as a 4-byte, IEEE 754 , binary floating point number. It provides 6 to 9 decimal digits of approximate precision. In contrast, DOUBLE provides 15 to 19 digits of approximate precision. REAL also supports infinity, -infinity, and NaN.

DOUBLE is a FairCom database field type containing a signed floating point number, such as -179769313.48623158 or 2.2250738585072014e-308. It is stored in a record as an 8-byte, IEEE 754 , binary floating point number. It supports a wide range of numbers and its calculations are fast. It provides 15 to 19 digits of approximate precision. It supports infinity, -infinity, and NaN.

TINYINT is a FairCom database field type containing a signed integer number, such as -128. It is stored in a record as a signed 8-bit integer number with a range from -128 to 127.

SMALLINT is a FairCom database field type containing a signed integer number, such as -32768. It is stored in a record as a signed 16-bit integer number with a range from -32,768 to 32,767.

INTEGER is a FairCom database field type containing a signed integer number, such as -2147483648. It is stored in a record as a signed 32-bit integer number with a range from -2,147,483,648 to 2,147,483,647.

BIGINT is a FairCom database field type containing a signed integer number, such as -9223372036854770000. It is stored in a record as a signed 64-bit integer number with a range from -9,223,372,036,854,770,000 to 9,223,372,036,854,770,000.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

MONEY is a FairCom database field type containing a signed decimal number, such as -12345678900.0001. It is stored in a record as a signed, fixed-point decimal number with 32 digits of precision. It consumes 19 bytes of storage. The "scale" property specifies 2 or 4 digits to the right of the decimal point. The remainder of the precision is to the left of the decimal point.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

REAL is a FairCom database field type containing a signed floating point number, such as -34028234.664 or 1.1754943508e-38. It is stored in a record as a 4-byte, IEEE 754 , binary floating point number. It provides 6 to 9 decimal digits of approximate precision. In contrast, DOUBLE provides 15 to 19 digits of approximate precision. REAL also supports infinity, -infinity, and NaN.

DOUBLE is a FairCom database field type containing a signed floating point number, such as -179769313.48623158 or 2.2250738585072014e-308. It is stored in a record as an 8-byte, IEEE 754 , binary floating point number. It supports a wide range of numbers and its calculations are fast. It provides 15 to 19 digits of approximate precision. It supports infinity, -infinity, and NaN.

TINYINT is a FairCom database field type containing a signed integer number, such as -128. It is stored in a record as a signed 8-bit integer number with a range from -128 to 127.

SMALLINT is a FairCom database field type containing a signed integer number, such as -32768. It is stored in a record as a signed 16-bit integer number with a range from -32,768 to 32,767.

INTEGER is a FairCom database field type containing a signed integer number, such as -2147483648. It is stored in a record as a signed 32-bit integer number with a range from -2,147,483,648 to 2,147,483,647.

BIGINT is a FairCom database field type containing a signed integer number, such as -9223372036854770000. It is stored in a record as a signed 64-bit integer number with a range from -9,223,372,036,854,770,000 to 9,223,372,036,854,770,000.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

MONEY is a FairCom database field type containing a signed decimal number, such as -12345678900.0001. It is stored in a record as a signed, fixed-point decimal number with 32 digits of precision. It consumes 19 bytes of storage. The "scale" property specifies 2 or 4 digits to the right of the decimal point. The remainder of the precision is to the left of the decimal point.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

REAL is a FairCom database field type containing a signed floating point number, such as -34028234.664 or 1.1754943508e-38. It is stored in a record as a 4-byte, IEEE 754 , binary floating point number. It provides 6 to 9 decimal digits of approximate precision. In contrast, DOUBLE provides 15 to 19 digits of approximate precision. REAL also supports infinity, -infinity, and NaN.

DOUBLE is a FairCom database field type containing a signed floating point number, such as -179769313.48623158 or 2.2250738585072014e-308. It is stored in a record as an 8-byte, IEEE 754 , binary floating point number. It supports a wide range of numbers and its calculations are fast. It provides 15 to 19 digits of approximate precision. It supports infinity, -infinity, and NaN.

TINYINT is a FairCom database field type containing a signed integer number, such as -128. It is stored in a record as a signed 8-bit integer number with a range from -128 to 127.

SMALLINT is a FairCom database field type containing a signed integer number, such as -32768. It is stored in a record as a signed 16-bit integer number with a range from -32,768 to 32,767.

INTEGER is a FairCom database field type containing a signed integer number, such as -2147483648. It is stored in a record as a signed 32-bit integer number with a range from -2,147,483,648 to 2,147,483,647.

BIGINT is a FairCom database field type containing a signed integer number, such as -9223372036854770000. It is stored in a record as a signed 64-bit integer number with a range from -9,223,372,036,854,770,000 to 9,223,372,036,854,770,000.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

MONEY is a FairCom database field type containing a signed decimal number, such as -12345678900.0001. It is stored in a record as a signed, fixed-point decimal number with 32 digits of precision. It consumes 19 bytes of storage. The "scale" property specifies 2 or 4 digits to the right of the decimal point. The remainder of the precision is to the left of the decimal point.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

A primary key is the primary identifier of a record in a database table. It is the primary way to look up records in a table. It is always indexed with a unique, non-null index that ensures each inserted record is uniquely identified. A primary key index includes one or more fields in a table.

The best practice is for a primary key to consist of one field named "id" that the server automatically populates with a unique identifier each time a record is inserted.

BIGINT is a FairCom database field type containing a signed integer number, such as -9223372036854770000. It is stored in a record as a signed 64-bit integer number with a range from -9,223,372,036,854,770,000 to 9,223,372,036,854,770,000.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

REAL is a FairCom database field type containing a signed floating point number, such as -34028234.664 or 1.1754943508e-38. It is stored in a record as a 4-byte, IEEE 754 , binary floating point number. It provides 6 to 9 decimal digits of approximate precision. In contrast, DOUBLE provides 15 to 19 digits of approximate precision. REAL also supports infinity, -infinity, and NaN.

DOUBLE is a FairCom database field type containing a signed floating point number, such as -179769313.48623158 or 2.2250738585072014e-308. It is stored in a record as an 8-byte, IEEE 754 , binary floating point number. It supports a wide range of numbers and its calculations are fast. It provides 15 to 19 digits of approximate precision. It supports infinity, -infinity, and NaN.

MONEY is a FairCom database field type containing a signed decimal number, such as -12345678900.0001. It is stored in a record as a signed, fixed-point decimal number with 32 digits of precision. It consumes 19 bytes of storage. The "scale" property specifies 2 or 4 digits to the right of the decimal point. The remainder of the precision is to the left of the decimal point.

TINYINT is a FairCom database field type containing a signed integer number, such as -128. It is stored in a record as a signed 8-bit integer number with a range from -128 to 127.

SMALLINT is a FairCom database field type containing a signed integer number, such as -32768. It is stored in a record as a signed 16-bit integer number with a range from -32,768 to 32,767.

INTEGER is a FairCom database field type containing a signed integer number, such as -2147483648. It is stored in a record as a signed 32-bit integer number with a range from -2,147,483,648 to 2,147,483,647.

BIGINT is a FairCom database field type containing a signed integer number, such as -9223372036854770000. It is stored in a record as a signed 64-bit integer number with a range from -9,223,372,036,854,770,000 to 9,223,372,036,854,770,000.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

REAL is a FairCom database field type containing a signed floating point number, such as -34028234.664 or 1.1754943508e-38. It is stored in a record as a 4-byte, IEEE 754 , binary floating point number. It provides 6 to 9 decimal digits of approximate precision. In contrast, DOUBLE provides 15 to 19 digits of approximate precision. REAL also supports infinity, -infinity, and NaN.

DOUBLE is a FairCom database field type containing a signed floating point number, such as -179769313.48623158 or 2.2250738585072014e-308. It is stored in a record as an 8-byte, IEEE 754 , binary floating point number. It supports a wide range of numbers and its calculations are fast. It provides 15 to 19 digits of approximate precision. It supports infinity, -infinity, and NaN.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

TINYINT is a FairCom database field type containing a signed integer number, such as -128. It is stored in a record as a signed 8-bit integer number with a range from -128 to 127.

SMALLINT is a FairCom database field type containing a signed integer number, such as -32768. It is stored in a record as a signed 16-bit integer number with a range from -32,768 to 32,767.

INTEGER is a FairCom database field type containing a signed integer number, such as -2147483648. It is stored in a record as a signed 32-bit integer number with a range from -2,147,483,648 to 2,147,483,647.

BIGINT is a FairCom database field type containing a signed integer number, such as -9223372036854770000. It is stored in a record as a signed 64-bit integer number with a range from -9,223,372,036,854,770,000 to 9,223,372,036,854,770,000.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

MONEY is a FairCom database field type containing a signed decimal number, such as -12345678900.0001. It is stored in a record as a signed, fixed-point decimal number with 32 digits of precision. It consumes 19 bytes of storage. The "scale" property specifies 2 or 4 digits to the right of the decimal point. The remainder of the precision is to the left of the decimal point.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

MONEY is a FairCom database field type containing a signed decimal number, such as -12345678900.0001. It is stored in a record as a signed, fixed-point decimal number with 32 digits of precision. It consumes 19 bytes of storage. The "scale" property specifies 2 or 4 digits to the right of the decimal point. The remainder of the precision is to the left of the decimal point.

TINYINT is a FairCom database field type containing a signed integer number, such as -128. It is stored in a record as a signed 8-bit integer number with a range from -128 to 127.

SMALLINT is a FairCom database field type containing a signed integer number, such as -32768. It is stored in a record as a signed 16-bit integer number with a range from -32,768 to 32,767.

INTEGER is a FairCom database field type containing a signed integer number, such as -2147483648. It is stored in a record as a signed 32-bit integer number with a range from -2,147,483,648 to 2,147,483,647.

BIGINT is a FairCom database field type containing a signed integer number, such as -9223372036854770000. It is stored in a record as a signed 64-bit integer number with a range from -9,223,372,036,854,770,000 to 9,223,372,036,854,770,000.

DOUBLE is a FairCom database field type containing a signed floating point number, such as -179769313.48623158 or 2.2250738585072014e-308. It is stored in a record as an 8-byte, IEEE 754 , binary floating point number. It supports a wide range of numbers and its calculations are fast. It provides 15 to 19 digits of approximate precision. It supports infinity, -infinity, and NaN.

REAL is a FairCom database field type containing a signed floating point number, such as -34028234.664 or 1.1754943508e-38. It is stored in a record as a 4-byte, IEEE 754 , binary floating point number. It provides 6 to 9 decimal digits of approximate precision. In contrast, DOUBLE provides 15 to 19 digits of approximate precision. REAL also supports infinity, -infinity, and NaN.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

DOUBLE is a FairCom database field type containing a signed floating point number, such as -179769313.48623158 or 2.2250738585072014e-308. It is stored in a record as an 8-byte, IEEE 754 , binary floating point number. It supports a wide range of numbers and its calculations are fast. It provides 15 to 19 digits of approximate precision. It supports infinity, -infinity, and NaN.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

MONEY is a FairCom database field type containing a signed decimal number, such as -12345678900.0001. It is stored in a record as a signed, fixed-point decimal number with 32 digits of precision. It consumes 19 bytes of storage. The "scale" property specifies 2 or 4 digits to the right of the decimal point. The remainder of the precision is to the left of the decimal point.

NUMERIC is a FairCom database field type containing a signed decimal number, such as -12345678900.000000123. It is stored in a record as a signed, fixed-point number that always consumes 19 bytes of storage.

MONEY is a FairCom database field type containing a signed decimal number, such as -12345678900.0001. It is stored in a record as a signed, fixed-point decimal number with 32 digits of precision. It consumes 19 bytes of storage. The "scale" property specifies 2 or 4 digits to the right of the decimal point. The remainder of the precision is to the left of the decimal point.

TINYINT is a FairCom database field type containing a signed integer number, such as -128. It is stored in a record as a signed 8-bit integer number with a range from -128 to 127.

SMALLINT is a FairCom database field type containing a signed integer number, such as -32768. It is stored in a record as a signed 16-bit integer number with a range from -32,768 to 32,767.

INTEGER is a FairCom database field type containing a signed integer number, such as -2147483648. It is stored in a record as a signed 32-bit integer number with a range from -2,147,483,648 to 2,147,483,647.

BIGINT is a FairCom database field type containing a signed integer number, such as -9223372036854770000. It is stored in a record as a signed 64-bit integer number with a range from -9,223,372,036,854,770,000 to 9,223,372,036,854,770,000.

DOUBLE is a FairCom database field type containing a signed floating point number, such as -179769313.48623158 or 2.2250738585072014e-308. It is stored in a record as an 8-byte, IEEE 754 , binary floating point number. It supports a wide range of numbers and its calculations are fast. It provides 15 to 19 digits of approximate precision. It supports infinity, -infinity, and NaN.

REAL is a FairCom database field type containing a signed floating point number, such as -34028234.664 or 1.1754943508e-38. It is stored in a record as a 4-byte, IEEE 754 , binary floating point number. It provides 6 to 9 decimal digits of approximate precision. In contrast, DOUBLE provides 15 to 19 digits of approximate precision. REAL also supports infinity, -infinity, and NaN.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

CHAR is a FairCom database field type containing a fxed-length, padded string value, such as "my string". It is stored in a record as a series of UTF-8 characters. It has a fixed-length between 1 and 65,500 bytes, which is stored once in the table's header. If a value is smaller than its fixed length, the server uses padding to fill in missing bytes at the end.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

Padding is a feature of the CHAR and BINARY field types. These fieldtypes have a fixed-length that is specified when they are created. Padding allows an application to fill part of the value of one of these fields and the server will fill out the remaining length with a pad character. The pad character defaults to the 0x00 byte. Each table can have its own user-defined pad character.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

DATE is a FairCom database field type containing a date value, such as "2022-03-08". It is stored in a record as an unsigned 32-bit integer that represents a specific day in the Gregorian calendar. A date has three parts: year, month, and day. It does not include time or a timezone offset.

TIME is a FairCom database field type containing a time value, such as "15:35:02:00". It is stored in a record as a 32-bit unsigned integer that represents a specific millisecond in a day. A time has four parts: hour, minute, second, and millisecond which represent the number of milliseconds after midnight. It does not include a date or a timezone offset.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

DATE is a FairCom database field type containing a date value, such as "2022-03-08". It is stored in a record as an unsigned 32-bit integer that represents a specific day in the Gregorian calendar. A date has three parts: year, month, and day. It does not include time or a timezone offset.

TIME is a FairCom database field type containing a time value, such as "15:35:02:00". It is stored in a record as a 32-bit unsigned integer that represents a specific millisecond in a day. A time has four parts: hour, minute, second, and millisecond which represent the number of milliseconds after midnight. It does not include a date or a timezone offset.

TIMESTAMP is a FairCom database field type. It is stored in a record as a 64-bit number that represents a specific DATE and TIME. It does not include a timezone offset.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

DATE is a FairCom database field type containing a date value, such as "2022-03-08". It is stored in a record as an unsigned 32-bit integer that represents a specific day in the Gregorian calendar. A date has three parts: year, month, and day. It does not include time or a timezone offset.

TIME is a FairCom database field type containing a time value, such as "15:35:02:00". It is stored in a record as a 32-bit unsigned integer that represents a specific millisecond in a day. A time has four parts: hour, minute, second, and millisecond which represent the number of milliseconds after midnight. It does not include a date or a timezone offset.

TIMESTAMP is a FairCom database field type. It is stored in a record as a 64-bit number that represents a specific DATE and TIME. It does not include a timezone offset.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

DATE is a FairCom database field type containing a date value, such as "2022-03-08". It is stored in a record as an unsigned 32-bit integer that represents a specific day in the Gregorian calendar. A date has three parts: year, month, and day. It does not include time or a timezone offset.

TIME is a FairCom database field type containing a time value, such as "15:35:02:00". It is stored in a record as a 32-bit unsigned integer that represents a specific millisecond in a day. A time has four parts: hour, minute, second, and millisecond which represent the number of milliseconds after midnight. It does not include a date or a timezone offset.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

DATE is a FairCom database field type containing a date value, such as "2022-03-08". It is stored in a record as an unsigned 32-bit integer that represents a specific day in the Gregorian calendar. A date has three parts: year, month, and day. It does not include time or a timezone offset.

TIME is a FairCom database field type containing a time value, such as "15:35:02:00". It is stored in a record as a 32-bit unsigned integer that represents a specific millisecond in a day. A time has four parts: hour, minute, second, and millisecond which represent the number of milliseconds after midnight. It does not include a date or a timezone offset.

TIMESTAMP is a FairCom database field type. It is stored in a record as a 64-bit number that represents a specific DATE and TIME. It does not include a timezone offset.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

Padding is a feature of the CHAR and BINARY field types. These fieldtypes have a fixed-length that is specified when they are created. Padding allows an application to fill part of the value of one of these fields and the server will fill out the remaining length with a pad character. The pad character defaults to the 0x00 byte. Each table can have its own user-defined pad character.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

A record contains data about one thing. A record describes the attributes of a thing using one or more fields. Zero or more records exist in a table; thus, a table contains data about zero or more things.

Different systems represent records differently. A JSON database represents each record as a JSON document. SQL represents each record as a row containing one or more columns of data. ISAM represents each record as a binary buffer of raw bytes.

FairCom products are unique because the FairCom database engine simultaneously supports these different record formats. The same record can be updated and queried simultaneously as JSON, a SQL row, or a binary buffer using the JSON DB API.

The JSON DB API uses JSON over HTTP to manage databases, tables, indexes, records, queries, cursors, and transactions. It is available in all FairCom products.

This API is part of FairCom's family of JSON APIs.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Indexed Sequential Access Method (ISAM) is FairCom's primary ACE API. ISAM uses the Record Buffer Method, which gives the application full control over the contents of the entire record buffer to store structured or unstructured data.

FairCom's ISAM API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's ISAM API works best in the C and C++ languages.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

The c-tree Database API (CTDB API) is FairCom's database API in the ACE family of APIs. It provides high performance with less code than the FairCom's ISAM API. The CTDB API introduces database concepts that are compatible with SQL. It requires records to contain predefined field structures. FairCom's CTDB API provides full control over record processing. This allows developers to implement data processing algorithms that are tailored to precise application needs, and this allows an application to achieve unrivaled performance. FairCom's CTDB API works well in a variety of languages, such as C, C++, Java, C#, and Visual Basic.

FairCom ACE APIs include ISAM, CTDB, and Low-level ACE API.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

A JSON value is the building block of JSON . A JSON value can stand alone or can be nested inside another JSON value.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

A JSON value is the building block of JSON . A JSON value can stand alone or can be nested inside another JSON value.

JSON consists of one or more JSON values that can be nested inside each other.

Each value is one of the data types: JSON object, JSON array, JSON string, JSON number, JSON Boolean, or JSON null.

A JSON object is a set of JSON properties. Each JSON property in an object must have a unique name. An object starts with the { character, contains zero or more properties separated by the comma (, ) character, and ends with the } character.

A JSON array contains one or more JSON values. Each JSON value may be any JSON type. An array starts with the [ character, contains zero or more values separated by the comma (, ) character, and ends with the ] character, such as [ 1, 2, 3] or [ "a", "b", "c"].

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

JSON consists of one or more JSON values that can be nested inside each other.

Each value is one of the data types: JSON object, JSON array, JSON string, JSON number, JSON Boolean, or JSON null.

A JSON object is a set of JSON properties. Each JSON property in an object must have a unique name. An object starts with the { character, contains zero or more properties separated by the comma (, ) character, and ends with the } character.

A JSON array contains one or more JSON values. Each JSON value may be any JSON type. An array starts with the [ character, contains zero or more values separated by the comma (, ) character, and ends with the ] character, such as [ 1, 2, 3] or [ "a", "b", "c"].

A JSON string value is a sequence of UTF-8 characters enclosed by double quotes.

A JSON number value is a signed, decimal floating point number. It is represented as a sequence of ASCII numeric digits with an optional + or - character at the beginning and an optional decimal point in the middle, such as -91.2247.

A JSON Boolean value is true or false.

A JSON null value is null.

A JSON value is the building block of JSON . A JSON value can stand alone or can be nested inside another JSON value.

JSON consists of one or more JSON values that can be nested inside each other.

Each value is one of the data types: JSON object, JSON array, JSON string, JSON number, JSON Boolean, or JSON null.

A JSON property has a name and a value where the name may be any string value and the value may be set to any JSON type.

JSON consists of one or more JSON values that can be nested inside each other.

Each value is one of the data types: JSON object, JSON array, JSON string, JSON number, JSON Boolean, or JSON null.

JSON consists of one or more JSON values that can be nested inside each other.

Each value is one of the data types: JSON object, JSON array, JSON string, JSON number, JSON Boolean, or JSON null.

A JSON object is a set of JSON properties. Each JSON property in an object must have a unique name. An object starts with the { character, contains zero or more properties separated by the comma (, ) character, and ends with the } character.

A JSON array contains one or more JSON values. Each JSON value may be any JSON type. An array starts with the [ character, contains zero or more values separated by the comma (, ) character, and ends with the ] character, such as [ 1, 2, 3] or [ "a", "b", "c"].

A JSON string value is a sequence of UTF-8 characters enclosed by double quotes.

A JSON number value is a signed, decimal floating point number. It is represented as a sequence of ASCII numeric digits with an optional + or - character at the beginning and an optional decimal point in the middle, such as -91.2247.

A JSON Boolean value is true or false.

A JSON null value is null.

A JSON object is a set of JSON properties. Each JSON property in an object must have a unique name. An object starts with the { character, contains zero or more properties separated by the comma (, ) character, and ends with the } character.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

Hypertext Transfer Protocol (HTTP) is a standard request-response protocol that works on top of TCP/IP. It allows a client computer to send a request to a server computer, which in turn, replies to the request. The purpose of HTTP is to allow software to ask questions and receive answers.

Hypertext Transfer Protocol (HTTP) is a standard request-response protocol that works on top of TCP/IP. It allows a client computer to send a request to a server computer, which in turn, replies to the request. The purpose of HTTP is to allow software to ask questions and receive answers.

Application Programming Interface (API) is a type of software interface that provides a service to other software. 

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A primary key is the primary identifier of a record in a database table. It is the primary way to look up records in a table. It is always indexed with a unique, non-null index that ensures each inserted record is uniquely identified. A primary key index includes one or more fields in a table.

The best practice is for a primary key to consist of one field named "id" that the server automatically populates with a unique identifier each time a record is inserted.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

JavaScript Object Notation (JSON) is a simple format for representing data. It requires very little markup and is flexible enough to represent the majority of data structures. It is self-describing, which makes it ideal for schemaless applications and search. It can optionally be paired with a schema to define an expected structure.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

Structured Query Language (SQL) is a standardized programming language that is used to manage relational databases and perform various operations on the data in them.

FairCom's SQL engine is ANSI compliant and has almost all SQL features up through the SQL:2003 standard.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

A database is a set of data that is managed by a database server. A database contains data that is organized into tables, records, and fields. A database is a huge composite data type that represents a group of interconnected objects. A database allows records to be joined together for querying, searching, and processing by users, applications, and services.

A database is a security container that controls which accounts have permissions to access specific data.

The Record Buffer Method is a technique for an application (typically C or C++) to retrieve a record from a file on disk and load it into an application's record buffer for reading and editing. When an application has finished editing the buffer, it writes the buffer back to disk. Because an application allocates a buffer in RAM, the Record Buffer Method is the fastest way to map data on disk to data in an application.

An application typically uses an API, such as FairCom's ISAM or CTDB API, to manage the process of reading and writing records to disk. A mature API can batch process multiple records at a time using arrays of buffers. The Record Buffer Method is exceptionally fast, efficient, and provides predictable performance because it transfers data directly from RAM to disk and vice versa.