DRAFT lightblue specifications
Introduction
1.
Language Specification
1.1.
Metadata
1.1.1.
entityInfo
1.1.1.1.
datastore
1.1.1.2.
enums
1.1.1.3.
hooks
1.1.1.4.
indexes
1.1.2.
schema
1.1.2.1.
access
1.1.2.2.
status
1.1.2.3.
version
1.1.2.4.
fields
1.1.2.4.1.
access
1.1.2.4.2.
constraints
1.1.2.4.3.
simple field
1.1.2.4.4.
container field
1.1.2.4.5.
reference field
1.2.
Data
1.2.1.
Query
1.2.1.1.
Field Comparisons with Arrays
1.2.2.
Projection
1.2.3.
Sort
1.2.4.
Range
1.2.5.
Update
1.2.6.
Execution
1.3.
Error
2.
REST Specification
2.1.
General
2.2.
Metadata
2.2.1.
Get Entity Dependencies Graph
2.2.2.
Get Entity Roles
2.2.3.
Get Entity Names
2.2.4.
Get Versions for Entity
2.2.5.
Get Metadata for Entity Version
2.2.6.
Create New Metadata
2.2.7.
Create New Schema
2.2.8.
Update Entity Info
2.2.9.
Update Schema Status
2.2.10.
Delete Default Version for Entity
2.2.11.
Update Default Version for Entity
2.2.12.
Delete Entity
2.3.
Data
2.3.1.
Insert New Data
2.3.2.
Save Existing Entity
2.3.3.
POST: Update Existing Entity
2.3.4.
Find (Simple)
2.3.5.
Find (Complex)
2.3.6.
Delete Data
2.3.7.
Bulk request
2.3.8.
Generate value
2.4.
Locking
2.4.1.
Acquire
2.4.2.
Release
2.4.3.
Get Lock Count
2.4.4.
Ping
3.
Backend Specifications
3.1.
MongoDB
3.1.1.
Metadata
3.2.
RDBMS
3.2.1.
Controller Design
3.2.1.1.
Data Types
3.2.1.2.
Data Structures
3.2.1.3.
Field Mappings
3.2.1.4.
Scenario: Simple
3.2.1.5.
Scenario: PK Generation by DB
3.2.1.6.
Scenario: PK Generation by Sequence
3.2.1.7.
Scenario: Array - PK
3.2.1.8.
Scenario: Array - No PK
3.2.1.9.
Scenario: Array - 2D
3.2.1.10.
Scenario: Dilution
3.2.1.11.
Scenario: Merge
3.2.1.12.
Scenario: PL/SQL
3.3.
LDAP
3.3.1.
Configure
3.3.2.
Metadata
3.3.3.
CRUD Operation Examples
Powered by
GitBook
DRAFT lightblue specifications
Scenario: Dilution
Summary: fewer tables in RDBMS than objects or arrays in lightblue metadata