| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
f_a_prepare_view().
|
|
|
|
| |
hook_field_prepare_view().
|
| |
|
|
|
|
| |
more consistent.
|
| |
|
|
|
|
| |
hook_field_prepare_view().
|
|
|
|
| |
field_default_validate().
|
| |
|
|
|
|
| |
arrays to increase performance (and to clean-up the code).
|
|
|
|
| |
compliance with standards.
|
|
|
|
| |
space.
|
|
|
|
| |
can't ever pass in another type of class.
|
| |
|
| |
|
|
|
|
| |
field_attach_query(). Was ready before code freeze.
|
| |
|
|
|
|
| |
avoid users rendering their site unusable.
|
| |
|
|
|
|
| |
argument 2 for field_delete_instance() in node_configure_fields().
|
| |
|
|
|
|
| |
in field forms.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
and moving non-crud functions.
|
|
|
|
| |
other types of stuff to render() structures.
|
|
|
|
| |
hook_field_attach_form.
|
| |
|
|
|
|
| |
function registry. While the hope was that this would result in improved performance for low-end hosts, it comes at the expense of critical development experience problems and less benefit than something like APC. Class registry remains intact to facilitate autoloading.
|
|
|
|
| |
registry rip. Let's try that again.
|
| |
|
|
|
|
| |
from field API.
|
|
|
|
| |
fields to Field API.
|
|
|
|
| |
CORE! OH YEAH! :D
|
| |
|
| |
|
| |
|
|
|
|
| |
field hooks are called incorrectly (or not at all).
|
|
|
|
| |
follow-up patch with bugfixes and tests.
|
| |
|
| |
|
|
|
|
| |
Well-documented and tested.
|
| |
|
|
|
|
| |
multiple cache IDs at once (with tests).
|
| |
|
| |
|
|
|
|
| |
Feel good moment!
|
| |
|
| |
|
|
|
|
| |
necessary because we can't assume fields will be stored in a database, due to pluggable storage backends.
|
|
|
|
| |
autoload feature.
|