Liking cljdoc? Tell your friends :D
kasandra.rules
- -session-from
- add-column-to-table
- add-columns-to-secondary-tables
- add-new-columns-to-view
- cascade-add-column-from-table-to-view
- cascade-drop-column-from-table-to-view
- cascade-table-drop-to-secondary-tables
- cascade-table-drop-to-views
- ColumnExists
- columns-in-primary-key?
- ColumnsInDerivedTable
- ColumnsInPrimaryKey
- ColumnsNotPresent
- create-table
- create-view
- create-views
- drop-column-from-table
- drop-table
- drop-views
- effects
- fire-rules
- insert
- intents
- intersect-columns
- intersect-columns*
- make-session
- order-after
- order-before
- Problem
- problem-when-adding-column-clashing-name
- problem-when-dropping-columns-in-view-primary-key
- problem-when-dropping-nonexistent-columns
- problem-when-removing-columns-from-lookup+unique-key-tables
- problems
- RecreateView
- relations
- remove-columns-from-secondary-tables
- remove-columns-from-view
- run-session-for
- summarize
- summarize-or-throw
- table-alread-exists
- table-view-relation
- TableAlreadyExists
- view-already-exists
- ViewAlreadyExists
- views-of-table
kasandra.rules.effects
Effects is the result of intents.
Ordering
The collection of effects can potentially be grouped into groups determined by the value under :effects/order.
The possible values are
:kasandra.rules.effects.order/before- should be applied before others- (no entry) - should be applied between others
:kasandra.rules.effects.order/after- should be applied before others.
Effects is the result of intents. # Ordering The collection of effects can potentially be grouped into groups determined by the value under :effects/order. The possible values are - `:kasandra.rules.effects.order/before` - should be applied before others - (no entry) - should be applied between others - `:kasandra.rules.effects.order/after` - should be applied before others.
kasandra.schema
Utilities for creating/navigating an in-memory represenatation of a Cassandra keyspace.
Notes: expect functions with match-X prefix to mostly do matching (via core.match).
Functions without the match-X prefix should return objects ready for use.
The CQL parser uses a slightly modified ANTLR grammar file available from
Utilities for creating/navigating an in-memory represenatation of a Cassandra keyspace. Notes: expect functions with `match-X` prefix to mostly do matching (via core.match). Functions without the `match-X` prefix should return objects ready for use. The CQL parser uses a slightly modified ANTLR grammar file available from https://github.com/antlr/grammars-v4/tree/master/cql3
- -column-names
- add-index
- CljAntlrOutput
- column-names
- create-table
- create-view
- deep-vectorize
- find-cql
- FormFinder
- lookup-by-name
- make-primary-key
- match-column-definition
- match-create-table
- match-create-table-clustering-key
- match-create-table-clustering-key-column
- match-create-table-option-item
- match-create-table-options
- match-create-table-with
- match-create-view
- match-option-hash-item
- match-primary-key
- match-view-clustering-order
- MatchBasedSchemaInfoProvider
- materialized-views
- primary-key-column-names
- schema-index
- schema-info
- SchemaParser
- search-schema-info
- syntax-comma?
- TableInfoProvider
- tables
- ViewInfoProvider
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close