• Introduction
  • What is DataMgr?
  • Exceptions
  • Contributions
• Basic Functionality
  • Getting Started
  • Structures in DataMgr
  • Save Data
  • Replace cfinsert/cfupdate
  • Replace SQL Inserts and Updates
  • Delete a Record
  • Get Records
  • Check Existence
  • Truncate Data
  • Change Sort Order
  • Save Many-to-Many Relationships
  • Update Multiple Records
  • Delete Multiple Records
  • Synchronize Database Structure (ActiveSchema / loadXml)
    • Define a Column
    • Remove a Column
    • Remove a Table
    • Define / Introspect Table
  • Seed Data
    • checkFields
  • Indexes
• Advanced Functionality
  • Logging
  • Simulated Database
  • Specials
    • Special Date Type
  • Relation Fields
    • Aggregates
    • Labels
    • Concatinations
    • Lists
    • Has / HasNot
    • Math
    • Now
    • Custom
  • "ftable"Attribute
  • Migrating Fields
  • Filters
  • Named Filters
  • Insert Custom SQL
  • SmartCache
  • Extending DataMgr
  • Database Adaptor
  • Is Deletable
• Informational Methods and Extra Functionality
  • Table Existence
  • Get Fields Meta Data
  • Run SQL Commands through DataMgr
  • Convert MS Word Character to ASCII
  • Get the Datasource that DataMgr is Using
  • Find out what Databases DataMgr supports
  • View DataMgr's Table Definitions
  • Get Methods SQL
  • Apply List Relations
• Change Log
  • Change Log

DataMgr Information

Download from RIA Forge

API Documentation

XML Schema

Demonstration Site

Blog Entries

DataMgr CFC Docs

Subscribe to DataMgr

Email:

Visit this group

Labels

Label Relation Fields allow you to retrieve a single related field from another table. For example, you could have a "Category" field that gets the value of the "CategoryName" field from a categories table based on a foreign key field in the current table.

Label relation fields are also using in saving data. So, if you pass in a value for "Category" (in our example) and a record in the categories table has a category name of the same value, then the foreign key field will be set to the appropriate value to indicate that category name.

If you add an "onMissing" value of "insert", then DataMgr will attempt to create a record in the related table for a new value if such a row doesn't already exist.

Attributes/Keys:

• type (required): "label".
• table (required): Name of table from which label data should be pulled.
• field (required): Name of the field holding the value of the label.
• join-field-local (required): Name of the field in local (main) table that should be used in join.
• join-field-remote (required): Name of the field in your remote (related) table that should be used in join.
• join-field (optional): If names of the join-field-local field and the join-field-remote field match, you can use join-field instead.

Example:

<field ColumnName="Category">
	<relation type="label" table="Cats" field="CatName" join-field="CatID" />
</field>

The Label Relation Field has an optional "onMissing" attribute to specify how DataMgr should behave if a value is passed in for this field that doesn't have a matching value in the related table.

• insert: DataMgr will create a record in the related table with this value
• error: DataMgr will throw an error informing you that the given value does not exist.
• ignore (default): DataMgr will leave the field blank.

"ftable" attribute

Note that the "join-field" attributes could be eliminated with the use of the "ftable" attribute.