| Commit message (Collapse) | Author | Age |
|
|
|
| |
Fixed Wrong schema description for {cache_field}.
|
| |
|
|
|
|
| |
catch: Fixed _field_info_collate_fields() memory usage.
|
| |
|
| |
|
|
|
|
| |
field_bundle_settings() out per bundle.
|
|
|
|
| |
module_enable() / _disable().
|
|
|
|
| |
deleted fields in installs upgraded from rc1.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
{field_config_entity_type()} abstraction.
|
| |
|
|
|
|
| |
node.
|
|
|
|
| |
taxonomy.
|
|
|
|
| |
upgrade path: comment.
|
|
|
|
| |
Tournoud: text column type doesn't reliably hold serialized variables.
|
| |
|
|
|
|
| |
compliance with standards.
|
|
|
|
| |
avoid users rendering their site unusable.
|
| |
|
|
|
|
|
|
| |
plach, profix898, mattyoung: added support for pluggable 'per field' storage engine. Comes with documentation and tests.
The Field Attach API uses the Field Storage API to perform all "database access". Each Field Storage API hook function defines a primitive database operation such as read, write, or delete. The default field storage module, field_sql_storage.module, uses the local SQL database to implement these operations, but alternative field storage backends can choose to represent the data in SQL differently or use a completely different storage mechanism such as a cloud-based database.
|
|
|
|
| |
weitzman: automatically install/uninstall schema.
|
|
|
|
| |
fields to Field API.
|
| |
|
| |
|
| |
|
|
|
|
| |
nominalizations from Docblocks.
|
| |
|
| |
|
|
|
|
| |
all .install files.
|
| |
|
| |
|
| |
|
|
floriant, chx, David Rothstein: initial field API patch. More work to be done, but ... oh my!
|