| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
file module.
|
|
|
|
| |
because it's faster.
|
|
|
|
| |
extensible from contrib - part II.
|
|
|
|
| |
files so we can get the upgrade path to work.
|
| |
|
| |
|
| |
|
|
|
|
| |
dereine, bjaspan: listing API for field API.
|
|
|
|
| |
causes fatal error.
|
| |
|
| |
|
|
|
|
| |
screen.
|
| |
|
| |
|
|
|
|
| |
is not documented.
|
|
|
|
| |
missing.
|
|
|
|
| |
'entity_type()' info in the serialized 'data' column.'
|
| |
|
|
|
|
| |
storage backend.
|
|
|
|
| |
without removing instance from all bundles.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
being pluggable.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
field_attach_query(). Was ready before code freeze.
|
|
|
|
| |
avoid users rendering their site unusable.
|
|
|
|
| |
argument 2 for field_delete_instance() in node_configure_fields().
|
| |
|
| |
|
|
|
|
| |
'translatable' property.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
updates.
|
| |
|
| |
|
|
|
|
| |
field_delete_(){field,instance}().
|
| |
|
| |
|
|
|
|
| |
fields to Field API.
|
|
|
|
| |
CORE! OH YEAH! :D
|
| |
|
| |
|
| |
|