Packages

•  package root

  

  

  Documentation/API for the Molecule library - a meta DSL for the Datomic database.

  Manual | scalamolecule.org | Github | Forum

  Definition Classes

  root

•  package molecule

  Molecule library - a Scala meta-DSL for the Datomic database.

  Molecule library - a Scala meta-DSL for the Datomic database.

  See api package for various api imports to start using Molecule.

  Sub-packages

  api		Molecule API.
  ast		Internal Molecule ASTs.
  boilerplate		Internal interfaces for auto-generated DSL boilerplate code.
  composition		Builder methods to compose molecules.
  exceptions		Exceptions thrown by Molecule.
  expression		Attribute expressions and operations.
  facade		Molecule facades to Datomic.
  factory		Implicit macro methods `m` to instantiate molecules from custom DSL molecule constructs.
  input		Input molecules awaiting input.
  macros		Internal macros generating molecule code from custom DSL molecule constructs.
  generic		Interfaces to generic information about datoms and Datomic database.
  ops		Internal operational helpers for transforming DSL to molecule.
  schema		Schema definition DSL.
  transform		Internal transformers from DSL to Model/Query/Transaction.
  util		Internal Java database functions for Datomic.

  Definition Classes

  root

•  package schema

  Schema definition DSL and API.

  Schema definition DSL and API.

  Definition Classes

  molecule

•  object definition

  Schema definition DSL.

  Schema definition DSL.
  
  Define Datomic database schema in a Schema Definition file.
  
  For small projects, the schema can be defined without partition definitions where all namespaces reside in a default tacit partition:

  package path.to.your.project
  import molecule.schema.definition._       // import schema definition DSL
  
  @InOut(1, 8)                              // Set input/output arity
  object SeattleDefinition {                // Schema definition object
  
    trait Person {                          // Namespace
      val name = oneString.fulltext   // String attribute definition with fulltext search
      val age  = oneInt                     // Int attribute definition
    }
  
    // Additional namespaces...
  }

  For larger projects, it is recommended to group namespaces in partitions:

  package path.to.your.project
  import molecule.schema.definition._
  
  @InOut(3, 15)
  object SeattleDefinition {
  
    object customer {
      trait Person {
        val name    = oneString.fulltext
        val age     = oneInt
        val address = one[Address]
        val bought  = many[products.Item]
      }
      trait Address {
        val street = oneString.fulltext
        val city   = oneInt
      }
      // ..more namespaces in the `customer` partition
    }
  
    object products {
      trait Item {
        val title   = oneString
        val inStock = oneInt
      }
      // ..more namespaces in the `products` partition
    }
  
    // Additional partitions...
  }

  Definition Classes

  schema

  See also

  Manual | Tests: Schema without partitions, Schema with partitions, Bidirectionals

• InOut
• many
• manyBi
• manyBiEdge
• manyBigDecimal
• manyBigInt
• manyBoolean
• manyByte
• manyDate
• manyDouble
• manyEnum
• manyFloat
• manyInt
• manyLong
• manyString
• manyURI
• manyUUID
• mapBigDecimal
• mapBigInt
• mapBoolean
• mapByte
• mapDate
• mapDouble
• mapFloat
• mapInt
• mapLong
• mapString
• mapURI
• mapUUID
• one
• oneBi
• oneBiEdge
• oneBigDecimal
• oneBigInt
• oneBoolean
• oneByte
• oneDate
• oneDouble
• oneEnum
• oneFloat
• oneInt
• oneLong
• oneString
• oneURI
• oneUUID
• optionBuilder
• refOptionBuilder
• target

molecule.schema.definition

mapFloat

Companion object mapFloat