This directory will contain the javascript and serverside components to enable client side validation of MMBase data types. This is work in progress. See 'datatypes' project.
| Datatype of Field | | ||
|---|---|---|---|
| 20th-century | | | Silly example (also used to test) Allow only dates from the previous century.. |
| 20th-century-pedantic | | | Pedantic version of 20th-century. Dates in the year 1900 are rejected, dates in the year 2000 are accepted. |
| age | | | This field can be used as a virtual field on a nodemanager with a birthdate field. This field then contains the 'age' in year. This is both settable and gettable. |
| binary | | | Blobs. Images, attachments, those kind of things. |
| birthdate | | | DataType specialized for storing birthdates. So, no times. Defaults to 30 years ago. No future dates are accepted. |
| boolean | | | Boolean fields can always contain only two possible values which could be interpreted in several ways (defaults to 'true' and 'false'). |
| byte | | | The values 0 - 255 are possible. |
| captcha | | | captcha |
| check | | | Boolean with no explicit enumeration. Will result in checkboxes. |
| checkequality | | | This is a field datatype that of which the value is only valid, if it is equal to the value of another field in this node. The other field's name is default empty but it can be changed by overriding the property 'field'. |
| checksum | | | The default 'checksum' datatype checksums the 'handle' field, but you can of course define your own (anonymously in the builder xml e.g.) for other fields. This is a read-only field which is automaticly filled on commit of the node. If you define this field as unique, then the effect is that a handle field which already is present in the database, cannot be saved. |
| colors | | | Colors as can be used in css. |
| components | | | The names of all available MMBase Framework Components |
| confirmpassword | | | This is a field datatype that of which the value is only valid, if it is equal to the value of another field in this node. The other field's name is default 'password' but it can be changed by overriding the property 'field'. |
| created | | | Read-only date-time field that contains the time of creation of the node. |
| creator | | | A ready-only field, which contains the user id of the user that created the node to wich the field belongs. |
| currency | | | Arbitrary precision numbers |
| currency_enforcescale | | | Arbitrary precision numbers |
| date | | | A date-time field that ignores the time part. |
| datetime | | | DateTime fields contain absolute points in time. TODO: say something about timezones here. Getting it as a String results in a formatted datetime according to the locale (of the cloud e.g.). |
| decimal | | | Arbitrary precision numbers |
| dirs | | | Enumeration for the 'dir' field of certain MMBase system builders. |
| double | | | Double precision floating point numbers. |
| duration | | | Durations are positive longs, which present a number of seconds. (for other units, we may have to introduce other datatypes). |
| dutch-zipcode | | | The valid values of such a field, are zip-codes as they are used in the Netherlands. |
| eline | | | A String that may not contain newlines (this is enforced). Practicly this will result in 'input type="text"' form entries. |
| email_type | | | Not so very big integer numbers. Common base for all kind of enumerations. |
| emailaddress | | | The valid values of such a field must be a valid email address. The current implemenation is by a rather simple regular expression. |
| enableddisabled | | | Boolean interpreted as enabled/disabled |
| eventtime | | | DateTime fields contain absolute points in time. TODO: say something about timezones here. Getting it as a String results in a formatted datetime according to the locale (of the cloud e.g.). |
| field | | | Mainly supplied for backwards compatibility. A String without further restrications. Practicly this will result in textarea form entries. |
| file | | | |
| filename | | | A filename field removes directory information on set. |
| filesize | | | Integer interpreted as a filesize. Results in a 'string' representation postfixed by 'KiB' etc. |
| filesize_deprecated | | | Integer interpreted as a filesize. Results in a 'string' representation postfixed by 'kbyte' etc. |
| float | | | Floating point numbers. |
| gender | | | A member of one or other sex, or rather being male or female. |
| historical | | | Historical dates, with a ERA designator. |
| hour_of_day | | | Stores an hour of the day (so a number from 0 to 23) |
| html | | | Principally, HTML could be valid XML. |
| index | | | String fields contain text. |
| integer | | | Not so very big integer numbers. Common base for all kind of enumerations. |
| internetaddress | | | Validates using javax.mail.internet.InternetAddress#parse. Can be used for (multiple) email-addresses. See javadoc. http://java.sun.com/products/javamail/javadocs/javax/mail/internet/InternetAddress.html#parse(java.lang.String) |
| ip | | | A ready-only field, which contains the IP address of the of the last user that changed the node to which the field belongs. |
| iso3166 | | | ISO 3166 language 2-letter country codes |
| iso639 | | | ISO 639 language 2-letter codes (sorted alphabeticly on the name of the language in the current locale) |
| lastmodified | | | Read-only date-time field that contains the most recent time at which this node was changed . |
| lastmodifier | | | A ready-only field, which contains the user id of the last user that changed the node to which the field belongs. |
| line | | | A String that may not contain newlines (though this is not enforced). Practicly this will result in 'input type="text"' form entries. |
| list | | | List valued |
| list[unknown] | | | list[unknown] |
| living-birthdate | | | DataType specialized for storing birthdates for people currently alive. Minimal value 140 years ago. Because this gives limited number of possible years, a dropdown for the year field becomes possible. |
| long | | | Longs can contain very big (positive and negative) integer numbers. |
| lowercaseuppercase | | | Silly example (also used to test) Strings are stored all lowercase, but showed all uppercase |
| md5password | | | In the database an MD5 of the value which is set into this field is set. If you try to get this value as a String, the empty String is returned. |
| media | | | Media types. |
| minute_of_hour | | | Stores a minute in an hour (so a number from 0 to 59) |
| mmxf | | | XML fields can be used for 'richtext' fields, or other fields which are (supposed to be) valid XML. |
| mmxfunp | | | XML fields can be used for 'richtext' fields, or other fields which are (supposed to be) valid XML. |
| node | | | Reference to an MMBase node. |
| nodemanagers | | | The names of all available MMBase NodeManagers |
| nodenumber | | | Just a node-field, but getting it as a String returns the node-number, rather then some odd toString of a Node object. |
| objecttype | | | If you define a virtual field with this type in your builder, then it actually works as an editable 'otype' field. In other words, the _type_ of the node becomes editable, which in some cases can come in handy. |
| onoff | | | Boolean interpreted as on/off |
| ordinals | | | 'First', 'second' etc. Implemented by a drop-down, so don't expect 'twothousandeth' to work. |
| origin-trace | | | Automaticly fills the java-stack trace in the value (if it is still null) on commit. This debug aid can be used to trace which code, and why, committed the node. |
| owner | | | The values of this field are restricted to the possible 'security contexts' of the current user as defined by the MMBase Security implementation. |
| phys_angle | | | An angle in radials (1 radian = 180 / π degrees). |
| phys_distance | | | Some distance, in the SI unit meters. Always positive. |
| phys_duration | | | An physical duration, in seconds. |
| phys_energy | | | |
| phys_mass | | | An physical mass. |
| phys_temperature | | | A physical temparature. |
| positive_integer | | | Not so very big integer numbers. Common base for all kind of enumerations. |
| reldef | | | Reference to an MMBase node of the type 'reldef'. |
| requiredfield | | | String fields contain text. |
| scale1-10 | | | A scale from 1 to 10. |
| security_context | | | Uses 'setContext' and 'getContext'. The idea is to use this type for a 'virtual' field. |
| sgender | | | Gender stored in a string 'M' or 'F'. |
| spells | | | Demo-enumeration for wizards. |
| string | | | String fields contain text. |
| time | | | A date-time field that ignores the date part. Actually this is stored as a time on 1970-01-01, but you can use this to indicate an hour of any day. Generic editors will not offer to edit the date parts of the date-time. |
| trimmedline | | | A String that may not contain newlines, after it is trimmed. Practicly this will result in 'input type="text"' form entries. |
| trimmedrequiredline | | | A String that may not contain newlines, after it is trimmed. After trimming, there must be at least one character |
| typedef | | | Reference to an MMBase node of the type 'typedef'. |
| unknown | | | unknown |
| user | | | Only nodes associated with users are possible. Default value is current user. |
| utctime | | | A date-time field that ignores the date part. Actually this is stored as a time on 1970-01-01, but you can use this to indicate an hour of any day. Generic editors will not offer to edit the date parts of the date-time. |
| verify_email | | | If this other field is changed, then this change will be ignored but in stead be stored on this 'verify email' field, together with a verification key. The verification can then be done by setting this key in this verify field (so, over the implicitely stored value). If the key is then the same as already stored, then the new email value is stored in the actual email field, and the verify field is emptied. |
| weekdays | | | Stores a day of the week (so a number from 1 to 7) |
| weeknumbers | | | Exotic specialization of 'date'. It will allow entering dates using the week-number and the name of the day. In controdiction to a more conventional notation with month and day of the month. |
| whitespacecollapser | | | If you set a value in a field with this datatype, then all occurences of one or more whitespace characters are removed before the value is committed to the database. |
| whitespacereplacer | | | If you set a value in a field with this datatype, then all occurences of one or more whitespace characters are replaced by one space before the value is committed to the database. |
| windowstate | | | String fields contain text. |
| xml | | | XML fields can be used for 'richtext' fields, or other fields which are (supposed to be) valid XML. |
| xmlfield | | | Adds processor to getting and setting as String, so that it looks like plain text then. |
| yesno | | | Boolean interpreted as yes/no |