TEST VERSION

Model settings

Target

What the generated code is for.

  • Selects the target database for the generated SQL code.
  • Selects the version of the naming convention to use for the generated code.
  • Selects if the generated code should be unitemporal (only changing time), bitemporal (both changing and positing time), or concurrent-reliance-temporal (one changing with several subjective positing times with uncertainty).

Features

What the generated code contains. Which of these apply depends on the target and the temporalization.

  • Selects if the generated code should contain a metadata reference or not.
  • Selects if the generated code should contain business views or not.
  • Selects if the views should contain aliases for knots that mimic the naming of regular attributes.
  • Selects if the generated code should contain triggers or not.
  • Selects if natural key attribute tables (materialized lookup tables for natural keys) should be generated.
  • Selects if equivalence should be allowed. Multiple values can be marked as having the same meaning, which for example is useful for multilingualism or multitenancy.
  • With decisiveness a positor holds a single assertion at a time, positive or negative, for an attribute of an anchor or nexus, or for the other roles of a tie, so an assertion of another value corrects the one held, which is retracted. Without it a positor may hold several at once, as long as they do not contradict each other: positive reliabilities count as they are, negative ones as one plus them, and together they may not exceed one.
  • Entity integrity adds constraints ensuring that no temporal duplicates can co-exist for the same entity and version, that no negative recording time intervals can be stored, and that there are no overlapping intervals with respect to recording time. This is highly recommended.
  • Selects whether to use partitioning of data. Applies to equivalents in uni-temporal and positors in concurrent-reliance-temporal modeling.

Names

How the generated tables and columns are named.

  • The default 'schema' to use for new items.
  • The suffix used for the columns that store changing time (versions).
  • The suffix used for the columns that store checksums.
  • The suffix used for the columns that store identities.
  • The prefix used for the columns that enable deletion.
  • The suffix used for tables that contain deleted rows.
  • The suffix used for the columns that store equivalents.
  • The suffix used for the column storing the point in time a posit was made.
  • The suffix used for the column storing the who made a posit.
  • The suffix used for the column storing reliability.
  • The suffix used for the computed column storing a single character '+', '-', or '?', indicating whether an assertion is positive, negative, or completely uncertain.

Types and values

The data types and the values used in the generated code.

  • The default 'data type' to use for identity columns.
  • The default changing time (versions) 'data type' for newly created and historized items.
  • The smallest common time type of all those used in the model.
  • How to get current, UTC or desired timestamping time from the database.
  • The 'data type' of the equivalents column.
  • The 'data type' for identities of posits used throughout the implementation.
  • The positing time (corrections) 'data type' used throughout the implementation.
  • The positor (one able to correct) 'data type' used throughout the implementation.
  • A 'data type' that can hold the desired degrees of reliability: in crt from -1 (certainly not) through 0 (complete uncertainty) to 1 (certainly), in bi 0 or 1.
  • The default value of reliability to use when it is not specified in an insert.
  • The default value of reliability to use when deleting information, which corresponds to being completely uncertain about a posit.

Defaults for new items

What a construct gets when it is added to the model.

  • Default for new items. Restatable items can store the exact same value for consecutive changing times. Unchecking this will introduce a constraint preventing restatements.
  • Default for new items. Idempotent items discard any attempt to insert or update a value that is identical to the latest one stored with respect to changing time.
  • Default for new items. Deletable items get additional update trigger logic, such that an update to null with a later changing time then the existing latest value will move rows into a corresponding deletion table.
  • Default for new items. Data may be encrypted at rest and this sets the default encryption group name for new items. A blank value indicates that no encryption should be used.
  • Default for new items. Assertive items get new annex rows every time a posit is made with a different positing time. Non-assertive items must also have a different reliability.

Advanced

The layout engine, for when the graph needs tuning, and a debug view of it.

  • Damping can be likened to friction and is needed in order to slow down the movement of the nodes.
  • The normal distance is the distance in pixels two nodes would be separated by if they were the only nodes in the graph.
  • Any node whose velocity is smaller than this number is assumed to have stopped.
  • The velocity needed for a stopped node to start moving again in a small graph.
  • The velocity needed for a stopped node to start moving again in a large graph.
  • The size of space partitions in number of normal distances.
  • The 'fuzziness' within which the size of the partitions are altered.
  • The effect of the force from other partitions on nodes in the current partition.
  • The stiffness of the edges control whether they behave like rubber bands or steel wires.
  • The number of frame redraws needed in the large SVG to trigger a redraw of the miniature.
  • Switching on advanced calculations lets you set more properties of nodes and edges, but at the cost of some performance.

Documentation

Models in this browser

Nothing is kept here yet. The models are kept in this browser only, not sent anywhere, and are gone if its data is cleared.

Paste a model from an agent

Paste what the agent gave you: the XML of the whole model, with or without text around it. It replaces the model that is here, and Undo brings that one back.

Anchor Modeling logotype