net.liftweb.ldap.LDAPProtoUser
Will be set to the type of the owner of the field
Will be set to the type of the owner of the field
Will be set to the type of the field
Will be set to the type of the field
The forced lower case column names
The forced lower case column names
Create an input field for the item
Create an input field for the item
Get the field that this prototypical field represents
Get the field that this prototypical field represents
the object to find the field on
If the field has a defined fieldId, append it
If the field has a defined fieldId, append it
Default read-only rendering of field
Default read-only rendering of field
Return the field name and field value, delimited by an '='
Return the field name and field value, delimited by an '='
Perform an atomic update of this Settable.
Perform an atomic update of this Settable. The current value is passed to the function and the ValueHolder is set to the result of the function. This is enclosed in the performAtomicOperation method which will, by default, synchronize this instance
Called when a column has been added to the database via Schemifier
Called when a column has been added to the database via Schemifier
Called when a column has indexed via Schemifier
Called when a column has indexed via Schemifier
Is the primary key autogenerated
Is the primary key autogenerated
The number of database columns that this field represents
The number of database columns that this field represents
What is the real class that corresponds to FieldType
What is the real class that corresponds to FieldType
Is the field a foreign key reference
Is the field a foreign key reference
Do we ignore the targetSQLType for setObject
Do we ignore the targetSQLType for setObject
override this method in indexed fields to indicate that the field has been saved
override this method in indexed fields to indicate that the field has been saved
Should the field be indexed?
Should the field be indexed?
Set to true if the field should be created as NOT NULL
Set to true if the field should be created as NOT NULL
Is the field the table's primary key
Is the field the table's primary key
The default value for the field
The default value for the field
Make the field dirty
Make the field dirty
Is the field dirty (has it been changed since the record was loaded from the database
Is the field dirty (has it been changed since the record was loaded from the database
The display name of this field (e.
The display name of this field (e.g., "First Name")
Called after the field is saved to the database
Called after the field is saved to the database
Does the "right thing" comparing mapped fields
Does the "right thing" comparing mapped fields
Given the driver type, return the string required to create the column in the database
Given the driver type, return the string required to create the column in the database
Given the driver type, return a list of SQL creation strings for the columns represented by this field
Given the driver type, return a list of SQL creation strings for the columns represented by this field
A unique 'id' for the field for form generation
A unique 'id' for the field for form generation
Return the owner of this field
Return the owner of this field
What form elements are we going to add to this field?
What form elements are we going to add to this field?
When building the form field, what's the input element's type attribute.
When building the form field, what's the input element's type attribute. Defaults to 'text', but change to 'email' or other HTML5 values.
Convert the field to its "context free" type (e.
Convert the field to its "context free" type (e.g., String, Int, Long, etc.) If there are no read permissions, the value will be obscured
The actual value of the field
The actual value of the field
Obscure the incoming value to a "safe" value (e.
Obscure the incoming value to a "safe" value (e.g., if there are not enough rights to view the entire social security number 123-45-5678, this method might return ***-**-*678
The value of the field when it was pulled from the DB
The value of the field when it was pulled from the DB
Should the field be ignored by the OR Mapper?
Should the field be ignored by the OR Mapper?
Get a JDBC friendly representation of the named field (this is used for MappedFields that correspond to more than 1 column in the database.
Get a JDBC friendly representation of the named field (this is used for MappedFields that correspond to more than 1 column in the database.)
-- the name of the field being mapped to
Get a JDBC friendly object for the part of this field that maps to the first column in the database
Get a JDBC friendly object for the part of this field that maps to the first column in the database
The name of this field
The name of this field
Perform an atomic operation on the Settable.
Perform an atomic operation on the Settable. By default synchronizes the instance, but it could use other mechanisms
Given the current execution state, can the field be read?
Given the current execution state, can the field be read?
Must be implemented to store the value of the field
Must be implemented to store the value of the field
Is the Field required (and will have a style designating it as such)
Is the Field required (and will have a style designating it as such)
Are we in "safe" mode (i.
Are we in "safe" mode (i.e., the value of the field can be read or written without any security checks.)
Set the field to the value
Set the field to the value
A list of functions that transform the value before it is set.
A list of functions that transform the value before it is set. The transformations are also applied before the value is used in a query. Typical applications of this are trimming and/or toLowerCase-ing strings
Attempt to figure out what the incoming value is and set the field to that value.
Attempt to figure out what the incoming value is and set the field to that value. Return true if the value could be assigned
Set the field to the Box value if the Box is Full
Set the field to the Box value if the Box is Full
Given the current context, should this field be displayed
Given the current context, should this field be displayed
Given the current state of things, should this field be shown
Given the current state of things, should this field be shown
Get the JDBC SQL Type for this field
Get the JDBC SQL Type for this field
Get the JDBC SQL Type for this field
Get the JDBC SQL Type for this field
Create an input field for the item
Create an input field for the item
The unique field id is the field name and the mapper name
The unique field id is the field name and the mapper name
Assignment from the underlying type.
Assignment from the underlying type. It's ugly, but:
field() = new_value
field set new_value
field.set(new_value)
are all the same
Is this an upload field so that a form that includes this field must be multi-part mime
Is this an upload field so that a form that includes this field must be multi-part mime
A validation helper.
A validation helper. Make sure the string is no more than a particular length and generate a validation issue if not.
A validation helper.
A validation helper. Make sure the string is at least a particular length and generate a validation issue if not.
Make sure the field matches a regular expression
Make sure the field matches a regular expression
Make sure that the field is unique in the database
Make sure that the field is unique in the database
Validate this field and return a list of Validation Issues
Validate this field and return a list of Validation Issues
What value was the field's value when it was pulled from the DB?
What value was the field's value when it was pulled from the DB?
Given the current execution state, can the field be written?
Given the current execution state, can the field be written?
(Since version 2.4) Just use apply(x openOr null). Will be removed in 2.5.
Get the value.
Get the value. Use get.
(Since version 2.6) Use get instead