2009-02-05 03:42:58 +00:00
< ? php
2009-02-08 21:22:59 +00:00
/**
* @ file
2009-02-10 03:16:15 +00:00
* Field CRUD API , handling field and field instance creation and deletion .
2009-02-08 21:22:59 +00:00
*/
2012-05-07 02:56:49 +00:00
use Drupal\field\FieldException ;
2012-09-12 09:18:04 +00:00
use Drupal\Core\Entity\EntityFieldQuery ;
2012-05-07 02:56:49 +00:00
2009-02-05 03:42:58 +00:00
/**
* @ defgroup field_crud Field CRUD API
* @ {
* Create , update , and delete Field API fields , bundles , and instances .
*
* Modules use this API , often in hook_install (), to create custom
2009-02-10 03:16:15 +00:00
* data structures . UI modules will use it to create a user interface .
2009-02-05 03:42:58 +00:00
*
* The Field CRUD API uses
2011-01-02 17:26:40 +00:00
* @ link field Field API data structures @ endlink .
2011-11-30 02:42:42 +00:00
*
2011-12-22 09:32:53 +00:00
* See @ link field Field API @ endlink for information about the other parts of
* the Field API .
2009-02-05 03:42:58 +00:00
*/
/**
2009-12-03 02:30:18 +00:00
* Creates a field .
2009-05-20 09:48:47 +00:00
*
* This function does not bind the field to any bundle ; use
* field_create_instance () for that .
2009-02-05 03:42:58 +00:00
*
* @ param $field
2010-01-03 23:31:17 +00:00
* A field definition array . The field_name and type properties are required .
2009-05-20 09:48:47 +00:00
* Other properties , if omitted , will be given the following default values :
* - cardinality : 1
* - locked : FALSE
* - indexes : the field - type indexes , specified by the field type ' s
* hook_field_schema () . The indexes specified in $field are added
* to those default indexes . It is possible to override the
* definition of a field - type index by providing an index with the
* same name , or to remove it by redefining it as an empty array
* of columns . Overriding field - type indexes should be done
2009-05-24 17:39:35 +00:00
* carefully , for it might seriously affect the site ' s performance .
2009-05-20 09:48:47 +00:00
* - settings : each omitted setting is given the default value defined in
* hook_field_info () .
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
* - storage :
2011-06-27 06:19:01 +00:00
* - type : the storage backend specified in the 'field_storage_default'
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
* system variable .
* - settings : each omitted setting is given the default value specified in
* hook_field_storage_info () .
2011-12-09 15:32:17 +00:00
*
2009-05-28 10:05:32 +00:00
* @ return
2010-01-03 23:31:17 +00:00
* The $field array with the id property filled in .
2011-12-09 15:32:17 +00:00
*
2012-05-07 02:56:49 +00:00
* @ throws Drupal\field\FieldException
2010-05-09 13:29:06 +00:00
*
2011-01-02 17:26:40 +00:00
* See : @ link field Field API data structures @ endlink .
2009-02-05 03:42:58 +00:00
*/
function field_create_field ( $field ) {
// Field name is required.
if ( empty ( $field [ 'field_name' ])) {
throw new FieldException ( 'Attempt to create an unnamed field.' );
}
2009-03-30 05:24:38 +00:00
// Field type is required.
if ( empty ( $field [ 'type' ])) {
throw new FieldException ( 'Attempt to create a field with no type.' );
}
2009-02-05 03:42:58 +00:00
// Field name cannot contain invalid characters.
2009-08-10 21:19:42 +00:00
if ( ! preg_match ( '/^[_a-z]+[_a-z0-9]*$/' , $field [ 'field_name' ])) {
throw new FieldException ( 'Attempt to create a field with invalid characters. Only lowercase alphanumeric characters and underscores are allowed, and only lowercase letters and underscore are allowed as the first character' );
2009-02-05 03:42:58 +00:00
}
2009-08-10 21:19:42 +00:00
// Field name cannot be longer than 32 characters. We use drupal_strlen()
// because the DB layer assumes that column widths are given in characters,
// not bytes.
if ( drupal_strlen ( $field [ 'field_name' ]) > 32 ) {
throw new FieldException ( t ( 'Attempt to create a field with a name longer than 32 characters: %name' ,
array ( '%name' => $field [ 'field_name' ])));
}
2009-02-05 03:42:58 +00:00
2009-05-28 10:05:32 +00:00
// Ensure the field name is unique over active and disabled fields.
// We do not care about deleted fields.
$prior_field = field_read_field ( $field [ 'field_name' ], array ( 'include_inactive' => TRUE ));
2009-02-05 03:42:58 +00:00
if ( ! empty ( $prior_field )) {
2009-09-07 15:50:52 +00:00
$message = $prior_field [ 'active' ] ?
t ( 'Attempt to create field name %name which already exists and is active.' , array ( '%name' => $field [ 'field_name' ])) :
t ( 'Attempt to create field name %name which already exists, although it is inactive.' , array ( '%name' => $field [ 'field_name' ]));
throw new FieldException ( $message );
2009-02-05 03:42:58 +00:00
}
2009-09-11 03:42:34 +00:00
// Disallow reserved field names. This can't prevent all field name
2010-02-12 05:38:10 +00:00
// collisions with existing entity properties, but some is better
2009-09-11 03:42:34 +00:00
// than none.
2009-10-31 16:06:36 +00:00
foreach ( entity_get_info () as $type => $info ) {
2010-03-27 05:52:50 +00:00
if ( in_array ( $field [ 'field_name' ], $info [ 'entity keys' ])) {
2009-09-11 03:42:34 +00:00
throw new FieldException ( t ( 'Attempt to create field name %name which is reserved by entity type %type.' , array ( '%name' => $field [ 'field_name' ], '%type' => $type )));
}
}
2009-02-05 03:42:58 +00:00
$field += array (
2010-03-27 05:52:50 +00:00
'entity_types' => array (),
2009-02-05 03:42:58 +00:00
'cardinality' => 1 ,
2009-08-22 00:58:55 +00:00
'translatable' => FALSE ,
2009-02-05 03:42:58 +00:00
'locked' => FALSE ,
'settings' => array (),
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
'storage' => array (),
'deleted' => 0 ,
2009-02-05 03:42:58 +00:00
);
2009-08-10 21:19:42 +00:00
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
// Check that the field type is known.
$field_type = field_info_field_types ( $field [ 'type' ]);
if ( ! $field_type ) {
throw new FieldException ( t ( 'Attempt to create a field of unknown type %type.' , array ( '%type' => $field [ 'type' ])));
}
2009-02-05 03:42:58 +00:00
// Create all per-field-type properties (needed here as long as we have
// settings that impact column definitions).
$field [ 'settings' ] += field_info_field_settings ( $field [ 'type' ]);
2009-05-20 09:48:47 +00:00
$field [ 'module' ] = $field_type [ 'module' ];
2009-02-05 03:42:58 +00:00
$field [ 'active' ] = 1 ;
2009-05-20 09:48:47 +00:00
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
// Provide default storage.
$field [ 'storage' ] += array (
'type' => variable_get ( 'field_storage_default' , 'field_sql_storage' ),
'settings' => array (),
);
// Check that the storage type is known.
$storage_type = field_info_storage_types ( $field [ 'storage' ][ 'type' ]);
if ( ! $storage_type ) {
throw new FieldException ( t ( 'Attempt to create a field with unknown storage type %type.' , array ( '%type' => $field [ 'storage' ][ 'type' ])));
}
// Provide default storage settings.
$field [ 'storage' ][ 'settings' ] += field_info_storage_settings ( $field [ 'storage' ][ 'type' ]);
$field [ 'storage' ][ 'module' ] = $storage_type [ 'module' ];
$field [ 'storage' ][ 'active' ] = 1 ;
2009-05-20 09:48:47 +00:00
// Collect storage information.
2010-09-04 15:40:52 +00:00
module_load_install ( $field [ 'module' ]);
2009-05-20 09:48:47 +00:00
$schema = ( array ) module_invoke ( $field [ 'module' ], 'field_schema' , $field );
2010-09-29 01:37:03 +00:00
$schema += array ( 'columns' => array (), 'indexes' => array (), 'foreign keys' => array ());
2009-05-20 09:48:47 +00:00
// 'columns' are hardcoded in the field type.
$field [ 'columns' ] = $schema [ 'columns' ];
2010-09-29 01:37:03 +00:00
// 'foreign keys' are hardcoded in the field type.
$field [ 'foreign keys' ] = $schema [ 'foreign keys' ];
2009-05-20 09:48:47 +00:00
// 'indexes' can be both hardcoded in the field type, and specified in the
// incoming $field definition.
$field += array (
'indexes' => array (),
);
$field [ 'indexes' ] += $schema [ 'indexes' ];
// The serialized 'data' column contains everything from $field that does not
// have its own column and is not automatically populated when the field is
// read.
$data = $field ;
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
unset ( $data [ 'columns' ], $data [ 'field_name' ], $data [ 'type' ], $data [ 'active' ], $data [ 'module' ], $data [ 'storage_type' ], $data [ 'storage_active' ], $data [ 'storage_module' ], $data [ 'locked' ], $data [ 'cardinality' ], $data [ 'deleted' ]);
2010-02-15 22:18:35 +00:00
// Additionally, do not save the 'bundles' property populated by
// field_info_field().
unset ( $data [ 'bundles' ]);
2009-05-20 09:48:47 +00:00
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
$record = array (
'field_name' => $field [ 'field_name' ],
'type' => $field [ 'type' ],
'module' => $field [ 'module' ],
'active' => $field [ 'active' ],
'storage_type' => $field [ 'storage' ][ 'type' ],
'storage_module' => $field [ 'storage' ][ 'module' ],
'storage_active' => $field [ 'storage' ][ 'active' ],
'locked' => $field [ 'locked' ],
'data' => $data ,
'cardinality' => $field [ 'cardinality' ],
2009-09-29 17:36:29 +00:00
'translatable' => $field [ 'translatable' ],
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
'deleted' => $field [ 'deleted' ],
);
2009-02-05 03:42:58 +00:00
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
// Store the field and get the id back.
drupal_write_record ( 'field_config' , $record );
$field [ 'id' ] = $record [ 'id' ];
2009-08-11 14:59:40 +00:00
2009-05-28 10:05:32 +00:00
// Invoke hook_field_storage_create_field after the field is
// complete (e.g. it has its id).
2009-09-22 08:44:04 +00:00
try {
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
// Invoke hook_field_storage_create_field after
// drupal_write_record() sets the field id.
module_invoke ( $storage_type [ 'module' ], 'field_storage_create_field' , $field );
2009-09-22 08:44:04 +00:00
}
catch ( Exception $e ) {
// If storage creation failed, remove the field_config record before
// rethrowing the exception.
db_delete ( 'field_config' )
-> condition ( 'id' , $field [ 'id' ])
-> execute ();
throw $e ;
}
2009-05-28 10:05:32 +00:00
2009-02-05 03:42:58 +00:00
// Clear caches
field_cache_clear ( TRUE );
2009-05-28 10:05:32 +00:00
2009-07-02 20:19:48 +00:00
// Invoke external hooks after the cache is cleared for API consistency.
module_invoke_all ( 'field_create_field' , $field );
2009-07-11 00:56:45 +00:00
2009-05-28 10:05:32 +00:00
return $field ;
2009-02-05 03:42:58 +00:00
}
2009-12-03 02:30:18 +00:00
/**
* Updates a field .
2009-09-26 15:57:39 +00:00
*
* Any module may forbid any update for any reason . For example , the
* field ' s storage module might forbid an update if it would change
* the storage schema while data for the field exists . A field type
* module might forbid an update if it would change existing data ' s
* semantics , or if there are external dependencies on field settings
* that cannot be updated .
*
* @ param $field
* A field structure . $field [ 'field_name' ] must provided ; it
* identifies the field that will be updated to match this
* structure . Any other properties of the field that are not
* specified in $field will be left unchanged , so it is not
* necessary to pass in a fully populated $field structure .
2012-05-07 02:56:49 +00:00
*
* @ throws Drupal\field\FieldException
*
2009-09-26 15:57:39 +00:00
* @ see field_create_field ()
*/
function field_update_field ( $field ) {
// Check that the specified field exists.
$prior_field = field_read_field ( $field [ 'field_name' ]);
if ( empty ( $prior_field )) {
throw new FieldException ( 'Attempt to update a non-existent field.' );
}
2009-10-31 16:06:36 +00:00
// Use the prior field values for anything not specifically set by the new
2009-09-26 15:57:39 +00:00
// field to be sure that all values are set.
$field += $prior_field ;
$field [ 'settings' ] += $prior_field [ 'settings' ];
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
// Some updates are always disallowed.
2009-09-26 15:57:39 +00:00
if ( $field [ 'type' ] != $prior_field [ 'type' ]) {
throw new FieldException ( " Cannot change an existing field's type. " );
}
2010-03-27 05:52:50 +00:00
if ( $field [ 'entity_types' ] != $prior_field [ 'entity_types' ]) {
throw new FieldException ( " Cannot change an existing field's entity_types property. " );
2010-01-30 02:22:01 +00:00
}
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
if ( $field [ 'storage' ][ 'type' ] != $prior_field [ 'storage' ][ 'type' ]) {
throw new FieldException ( " Cannot change an existing field's storage type. " );
}
2009-09-26 15:57:39 +00:00
// Collect the new storage information, since what is in
// $prior_field may no longer be right.
2010-09-04 15:40:52 +00:00
module_load_install ( $field [ 'module' ]);
2009-09-26 15:57:39 +00:00
$schema = ( array ) module_invoke ( $field [ 'module' ], 'field_schema' , $field );
$schema += array ( 'columns' => array (), 'indexes' => array ());
// 'columns' are hardcoded in the field type.
$field [ 'columns' ] = $schema [ 'columns' ];
// 'indexes' can be both hardcoded in the field type, and specified in the
// incoming $field definition.
$field += array (
'indexes' => array (),
);
$field [ 'indexes' ] += $schema [ 'indexes' ];
2009-09-30 12:26:36 +00:00
$has_data = field_has_data ( $field );
2009-09-26 15:57:39 +00:00
// See if any module forbids the update by throwing an exception.
foreach ( module_implements ( 'field_update_forbid' ) as $module ) {
$function = $module . '_field_update_forbid' ;
$function ( $field , $prior_field , $has_data );
}
// Tell the storage engine to update the field. Do this before
// saving the new definition since it still might fail.
2010-03-03 07:56:18 +00:00
$storage_type = field_info_storage_types ( $field [ 'storage' ][ 'type' ]);
module_invoke ( $storage_type [ 'module' ], 'field_storage_update_field' , $field , $prior_field , $has_data );
2009-09-26 15:57:39 +00:00
// Save the new field definition. @todo: refactor with
// field_create_field.
// The serialized 'data' column contains everything from $field that does not
// have its own column and is not automatically populated when the field is
// read.
$data = $field ;
unset ( $data [ 'columns' ], $data [ 'field_name' ], $data [ 'type' ], $data [ 'locked' ], $data [ 'module' ], $data [ 'cardinality' ], $data [ 'active' ], $data [ 'deleted' ]);
2010-02-15 22:18:35 +00:00
// Additionally, do not save the 'bundles' property populated by
// field_info_field().
unset ( $data [ 'bundles' ]);
2009-09-26 15:57:39 +00:00
$field [ 'data' ] = $data ;
// Store the field and create the id.
$primary_key = array ( 'id' );
drupal_write_record ( 'field_config' , $field , $primary_key );
// Clear caches
field_cache_clear ( TRUE );
2009-10-31 16:06:36 +00:00
2009-09-26 15:57:39 +00:00
// Invoke external hooks after the cache is cleared for API consistency.
2009-10-31 16:06:36 +00:00
module_invoke_all ( 'field_update_field' , $field , $prior_field , $has_data );
2009-09-26 15:57:39 +00:00
}
2009-02-05 03:42:58 +00:00
/**
2009-12-03 02:30:18 +00:00
* Reads a single field record directly from the database .
*
* Generally , you should use the field_info_field () instead .
2009-02-05 03:42:58 +00:00
*
2009-05-28 10:05:32 +00:00
* This function will not return deleted fields . Use
* field_read_fields () instead for this purpose .
*
2009-02-05 03:42:58 +00:00
* @ param $field_name
* The field name to read .
* @ param array $include_additional
* The default behavior of this function is to not return a field that
2009-05-28 10:05:32 +00:00
* is inactive . Setting
* $include_additional [ 'include_inactive' ] to TRUE will override this
2009-02-05 03:42:58 +00:00
* behavior .
* @ return
2010-01-03 23:31:17 +00:00
* A field definition array , or FALSE .
2009-02-05 03:42:58 +00:00
*/
function field_read_field ( $field_name , $include_additional = array ()) {
$fields = field_read_fields ( array ( 'field_name' => $field_name ), $include_additional );
return $fields ? current ( $fields ) : FALSE ;
}
/**
2009-12-03 02:30:18 +00:00
* Reads in fields that match an array of conditions .
2009-02-05 03:42:58 +00:00
*
* @ param array $params
* An array of conditions to match against .
* @ param array $include_additional
* The default behavior of this function is to not return fields that
* are inactive or have been deleted . Setting
* $include_additional [ 'include_inactive' ] or
* $include_additional [ 'include_deleted' ] to TRUE will override this
* behavior .
* @ return
2009-05-28 10:05:32 +00:00
* An array of fields matching $params . If
2010-01-03 23:31:17 +00:00
* $include_additional [ 'include_deleted' ] is TRUE , the array is keyed
2009-05-28 10:05:32 +00:00
* by field id , otherwise it is keyed by field name .
2009-02-05 03:42:58 +00:00
*/
function field_read_fields ( $params = array (), $include_additional = array ()) {
$query = db_select ( 'field_config' , 'fc' , array ( 'fetch' => PDO :: FETCH_ASSOC ));
$query -> fields ( 'fc' );
// Turn the conditions into a query.
foreach ( $params as $key => $value ) {
$query -> condition ( $key , $value );
}
if ( ! isset ( $include_additional [ 'include_inactive' ]) || ! $include_additional [ 'include_inactive' ]) {
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
$query
-> condition ( 'fc.active' , 1 )
-> condition ( 'fc.storage_active' , 1 );
2009-02-05 03:42:58 +00:00
}
2009-05-28 10:05:32 +00:00
$include_deleted = ( isset ( $include_additional [ 'include_deleted' ]) && $include_additional [ 'include_deleted' ]);
if ( ! $include_deleted ) {
2009-02-05 03:42:58 +00:00
$query -> condition ( 'fc.deleted' , 0 );
}
$fields = array ();
$results = $query -> execute ();
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
foreach ( $results as $record ) {
$field = unserialize ( $record [ 'data' ]);
$field [ 'id' ] = $record [ 'id' ];
$field [ 'field_name' ] = $record [ 'field_name' ];
$field [ 'type' ] = $record [ 'type' ];
$field [ 'module' ] = $record [ 'module' ];
$field [ 'active' ] = $record [ 'active' ];
$field [ 'storage' ][ 'type' ] = $record [ 'storage_type' ];
$field [ 'storage' ][ 'module' ] = $record [ 'storage_module' ];
$field [ 'storage' ][ 'active' ] = $record [ 'storage_active' ];
$field [ 'locked' ] = $record [ 'locked' ];
$field [ 'cardinality' ] = $record [ 'cardinality' ];
$field [ 'translatable' ] = $record [ 'translatable' ];
$field [ 'deleted' ] = $record [ 'deleted' ];
2009-02-05 03:42:58 +00:00
module_invoke_all ( 'field_read_field' , $field );
2009-05-20 09:48:47 +00:00
// Populate storage information.
2010-09-04 15:40:52 +00:00
module_load_install ( $field [ 'module' ]);
2009-05-20 09:48:47 +00:00
$schema = ( array ) module_invoke ( $field [ 'module' ], 'field_schema' , $field );
$schema += array ( 'columns' => array (), 'indexes' => array ());
$field [ 'columns' ] = $schema [ 'columns' ];
2009-02-05 03:42:58 +00:00
2009-05-28 10:05:32 +00:00
$field_name = $field [ 'field_name' ];
if ( $include_deleted ) {
$field_name = $field [ 'id' ];
}
$fields [ $field_name ] = $field ;
2009-02-05 03:42:58 +00:00
}
return $fields ;
}
/**
2009-12-03 02:30:18 +00:00
* Marks a field and its instances and data for deletion .
2009-02-05 03:42:58 +00:00
*
* @ param $field_name
* The field name to delete .
*/
function field_delete_field ( $field_name ) {
2009-09-09 11:37:34 +00:00
// Delete all non-deleted instances.
$field = field_info_field ( $field_name );
if ( isset ( $field [ 'bundles' ])) {
2010-02-11 17:44:47 +00:00
foreach ( $field [ 'bundles' ] as $entity_type => $bundles ) {
2009-10-15 12:44:36 +00:00
foreach ( $bundles as $bundle ) {
2010-02-11 17:44:47 +00:00
$instance = field_info_instance ( $entity_type , $field_name , $bundle );
2010-12-15 04:13:48 +00:00
field_delete_instance ( $instance , FALSE );
2009-10-15 12:44:36 +00:00
}
2009-09-09 11:37:34 +00:00
}
}
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
// Mark field data for deletion.
module_invoke ( $field [ 'storage' ][ 'module' ], 'field_storage_delete_field' , $field );
2009-05-28 10:05:32 +00:00
// Mark the field for deletion.
db_update ( 'field_config' )
2009-02-05 03:42:58 +00:00
-> fields ( array ( 'deleted' => 1 ))
-> condition ( 'field_name' , $field_name )
-> execute ();
2009-05-28 10:05:32 +00:00
2009-02-05 03:42:58 +00:00
// Clear the cache.
field_cache_clear ( TRUE );
2009-09-09 11:37:34 +00:00
module_invoke_all ( 'field_delete_field' , $field );
2009-02-05 03:42:58 +00:00
}
/**
* Creates an instance of a field , binding it to a bundle .
*
* @ param $instance
2010-03-27 05:52:50 +00:00
* A field instance definition array . The field_name , entity_type and
2009-10-15 12:44:36 +00:00
* bundle properties are required . Other properties , if omitted ,
* will be given the following default values :
2009-05-20 09:48:47 +00:00
* - label : the field name
* - description : empty string
* - required : FALSE
* - default_value_function : empty string
* - settings : each omitted setting is given the default value specified in
* hook_field_info () .
* - widget :
* - type : the default widget specified in hook_field_info () .
* - settings : each omitted setting is given the default value specified in
* hook_field_widget_info () .
* - display :
2010-05-23 19:10:23 +00:00
* Settings for the 'default' view mode will be added if not present , and
* each view mode in the definition will be completed with the following
* default values :
2009-05-20 09:48:47 +00:00
* - label : 'above'
* - type : the default formatter specified in hook_field_info () .
* - settings : each omitted setting is given the default value specified in
* hook_field_formatter_info () .
2010-05-23 19:10:23 +00:00
* View modes not present in the definition are left empty , and the field
* will not be displayed in this mode .
*
2009-05-28 10:05:32 +00:00
* @ return
2010-01-03 23:31:17 +00:00
* The $instance array with the id property filled in .
2011-12-09 15:32:17 +00:00
*
2012-05-07 02:56:49 +00:00
* @ throws Drupal\field\FieldException
2010-05-09 13:29:06 +00:00
*
2011-01-02 17:26:40 +00:00
* See : @ link field Field API data structures @ endlink .
2009-02-05 03:42:58 +00:00
*/
2012-09-27 03:47:21 +00:00
function field_create_instance ( & $instance ) {
2009-02-05 03:42:58 +00:00
$field = field_read_field ( $instance [ 'field_name' ]);
if ( empty ( $field )) {
2010-02-05 22:11:26 +00:00
throw new FieldException ( t ( " Attempt to create an instance of a field @field_name that doesn't exist or is currently inactive. " , array ( '@field_name' => $instance [ 'field_name' ])));
2009-02-05 03:42:58 +00:00
}
2009-10-15 12:44:36 +00:00
// Check that the required properties exists.
2010-03-27 05:52:50 +00:00
if ( empty ( $instance [ 'entity_type' ])) {
2010-05-31 07:59:27 +00:00
throw new FieldException ( t ( 'Attempt to create an instance of field @field_name without an entity type.' , array ( '@field_name' => $instance [ 'field_name' ])));
2009-10-15 12:44:36 +00:00
}
if ( empty ( $instance [ 'bundle' ])) {
throw new FieldException ( t ( 'Attempt to create an instance of field @field_name without a bundle.' , array ( '@field_name' => $instance [ 'field_name' ])));
}
2010-02-12 05:38:10 +00:00
// Check that the field can be attached to this entity type.
2010-03-27 05:52:50 +00:00
if ( ! empty ( $field [ 'entity_types' ]) && ! in_array ( $instance [ 'entity_type' ], $field [ 'entity_types' ])) {
2010-05-31 07:59:27 +00:00
throw new FieldException ( t ( 'Attempt to create an instance of field @field_name on forbidden entity type @entity_type.' , array ( '@field_name' => $instance [ 'field_name' ], '@entity_type' => $instance [ 'entity_type' ])));
2010-01-30 02:22:01 +00:00
}
2009-02-05 03:42:58 +00:00
2009-03-10 09:45:32 +00:00
// Set the field id.
$instance [ 'field_id' ] = $field [ 'id' ];
2009-06-12 08:39:40 +00:00
// Note that we do *not* prevent creating a field on non-existing bundles,
// because that would break the 'Body as field' upgrade for contrib
// node types.
2009-02-05 03:42:58 +00:00
// TODO: Check that the widget type is known and can handle the field type ?
// TODO: Check that the formatters are known and can handle the field type ?
2010-02-12 05:38:10 +00:00
// TODO: Check that the display view modes are known for the entity type ?
2009-02-05 03:42:58 +00:00
// Those checks should probably happen in _field_write_instance() ?
// Problem : this would mean that a UI module cannot update an instance with a disabled formatter.
2009-10-01 19:16:57 +00:00
// Ensure the field instance is unique within the bundle.
// We only check for instances of active fields, since adding an instance of
// a disabled field is not supported.
2010-03-27 05:52:50 +00:00
$prior_instance = field_read_instance ( $instance [ 'entity_type' ], $instance [ 'field_name' ], $instance [ 'bundle' ]);
2009-02-05 03:42:58 +00:00
if ( ! empty ( $prior_instance )) {
2010-02-05 22:11:26 +00:00
$message = t ( 'Attempt to create an instance of field @field_name on bundle @bundle that already has an instance of that field.' , array ( '@field_name' => $instance [ 'field_name' ], '@bundle' => $instance [ 'bundle' ]));
2009-09-07 15:50:52 +00:00
throw new FieldException ( $message );
2009-02-05 03:42:58 +00:00
}
_field_write_instance ( $instance );
// Clear caches
field_cache_clear ();
2009-03-30 03:44:55 +00:00
// Invoke external hooks after the cache is cleared for API consistency.
module_invoke_all ( 'field_create_instance' , $instance );
2009-05-28 10:05:32 +00:00
return $instance ;
2009-02-05 03:42:58 +00:00
}
2009-12-03 02:30:18 +00:00
/**
* Updates an instance of a field .
2009-02-05 03:42:58 +00:00
*
* @ param $instance
2010-01-03 23:31:17 +00:00
* An associative array representing an instance structure . The required
2009-02-05 03:42:58 +00:00
* keys and values are :
2010-10-25 00:09:12 +00:00
* - entity_type : The type of the entity the field is attached to .
* - bundle : The bundle this field belongs to .
* - field_name : The name of an existing field .
2009-03-10 09:45:32 +00:00
* Read - only_id properties are assigned automatically . Any other
* properties specified in $instance overwrite the existing values for
* the instance .
2010-10-25 00:09:12 +00:00
*
2012-05-07 02:56:49 +00:00
* @ throws Drupal\field\FieldException
2010-10-25 00:09:12 +00:00
*
2009-02-05 03:42:58 +00:00
* @ see field_create_instance ()
*/
function field_update_instance ( $instance ) {
// Check that the specified field exists.
$field = field_read_field ( $instance [ 'field_name' ]);
if ( empty ( $field )) {
2010-06-03 13:08:52 +00:00
throw new FieldException ( t ( 'Attempt to update an instance of a nonexistent field @field.' , array ( '@field' => $instance [ 'field_name' ])));
2009-02-05 03:42:58 +00:00
}
// Check that the field instance exists (even if it is inactive, since we
// want to be able to replace inactive widgets with new ones).
2010-03-27 05:52:50 +00:00
$prior_instance = field_read_instance ( $instance [ 'entity_type' ], $instance [ 'field_name' ], $instance [ 'bundle' ], array ( 'include_inactive' => TRUE ));
2009-02-05 03:42:58 +00:00
if ( empty ( $prior_instance )) {
2010-06-03 13:08:52 +00:00
throw new FieldException ( t ( " Attempt to update an instance of field @field on bundle @bundle that doesn't exist. " , array ( '@field' => $instance [ 'field_name' ], '@bundle' => $instance [ 'bundle' ])));
2009-02-05 03:42:58 +00:00
}
2009-03-10 09:45:32 +00:00
$instance [ 'id' ] = $prior_instance [ 'id' ];
$instance [ 'field_id' ] = $prior_instance [ 'field_id' ];
2009-02-05 03:42:58 +00:00
_field_write_instance ( $instance , TRUE );
// Clear caches.
field_cache_clear ();
2010-04-22 19:06:34 +00:00
module_invoke_all ( 'field_update_instance' , $instance , $prior_instance );
2009-02-05 03:42:58 +00:00
}
/**
2009-12-03 02:30:18 +00:00
* Stores an instance record in the field configuration database .
2009-02-05 03:42:58 +00:00
*
* @ param $instance
* An instance structure .
* @ param $update
* Whether this is a new or existing instance .
*/
2012-09-27 03:47:21 +00:00
function _field_write_instance ( & $instance , $update = FALSE ) {
2009-02-05 03:42:58 +00:00
$field = field_read_field ( $instance [ 'field_name' ]);
$field_type = field_info_field_types ( $field [ 'type' ]);
2012-09-26 19:39:39 +00:00
// Temporary workaround to allow incoming $instance as arrays or classed
// objects.
// @todo remove once the external APIs have been converted to use
// FieldInstance objects.
if ( is_object ( $instance ) && get_class ( $instance ) == 'Drupal\field\FieldInstance' ) {
$instance = $instance -> getArray ();
}
2009-02-05 03:42:58 +00:00
// Set defaults.
$instance += array (
'settings' => array (),
'display' => array (),
'widget' => array (),
'required' => FALSE ,
'label' => $instance [ 'field_name' ],
'description' => '' ,
'deleted' => 0 ,
);
// Set default instance settings.
$instance [ 'settings' ] += field_info_instance_settings ( $field [ 'type' ]);
// Set default widget and settings.
$instance [ 'widget' ] += array (
// TODO: what if no 'default_widget' specified ?
'type' => $field_type [ 'default_widget' ],
'settings' => array (),
);
2010-05-23 19:10:23 +00:00
// If no weight specified, make sure the field sinks at the bottom.
if ( ! isset ( $instance [ 'widget' ][ 'weight' ])) {
2010-09-11 00:03:42 +00:00
$max_weight = field_info_max_weight ( $instance [ 'entity_type' ], $instance [ 'bundle' ], 'form' );
2010-09-24 02:10:06 +00:00
$instance [ 'widget' ][ 'weight' ] = isset ( $max_weight ) ? $max_weight + 1 : 0 ;
2010-05-23 19:10:23 +00:00
}
2009-02-05 03:42:58 +00:00
// Check widget module.
$widget_type = field_info_widget_types ( $instance [ 'widget' ][ 'type' ]);
2009-10-01 19:16:57 +00:00
$instance [ 'widget' ][ 'module' ] = $widget_type [ 'module' ];
2009-02-05 03:42:58 +00:00
$instance [ 'widget' ][ 'settings' ] += field_info_widget_settings ( $instance [ 'widget' ][ 'type' ]);
2010-05-23 19:10:23 +00:00
// Make sure there are at least display settings for the 'default' view mode,
// and fill in defaults for each view mode specified in the definition.
2009-02-05 03:42:58 +00:00
$instance [ 'display' ] += array (
2010-05-23 19:10:23 +00:00
'default' => array (),
2009-02-05 03:42:58 +00:00
);
2009-12-26 16:50:09 +00:00
foreach ( $instance [ 'display' ] as $view_mode => $display ) {
2010-05-23 19:10:23 +00:00
$display += array (
2009-02-05 03:42:58 +00:00
'label' => 'above' ,
2010-05-23 19:10:23 +00:00
'type' => isset ( $field_type [ 'default_formatter' ]) ? $field_type [ 'default_formatter' ] : 'hidden' ,
2009-02-05 03:42:58 +00:00
'settings' => array (),
);
2010-05-23 19:10:23 +00:00
if ( $display [ 'type' ] != 'hidden' ) {
$formatter_type = field_info_formatter_types ( $display [ 'type' ]);
$display [ 'module' ] = $formatter_type [ 'module' ];
$display [ 'settings' ] += field_info_formatter_settings ( $display [ 'type' ]);
}
// If no weight specified, make sure the field sinks at the bottom.
if ( ! isset ( $display [ 'weight' ])) {
2010-09-11 00:03:42 +00:00
$max_weight = field_info_max_weight ( $instance [ 'entity_type' ], $instance [ 'bundle' ], $view_mode );
2010-09-24 02:10:06 +00:00
$display [ 'weight' ] = isset ( $max_weight ) ? $max_weight + 1 : 0 ;
2010-05-23 19:10:23 +00:00
}
$instance [ 'display' ][ $view_mode ] = $display ;
2009-02-05 03:42:58 +00:00
}
2009-05-20 09:48:47 +00:00
// The serialized 'data' column contains everything from $instance that does
// not have its own column and is not automatically populated when the
// instance is read.
2009-02-05 03:42:58 +00:00
$data = $instance ;
2010-03-28 11:54:06 +00:00
unset ( $data [ 'id' ], $data [ 'field_id' ], $data [ 'field_name' ], $data [ 'entity_type' ], $data [ 'bundle' ], $data [ 'deleted' ]);
2009-02-05 03:42:58 +00:00
$record = array (
2009-03-10 09:45:32 +00:00
'field_id' => $instance [ 'field_id' ],
2009-02-05 03:42:58 +00:00
'field_name' => $instance [ 'field_name' ],
2010-03-27 05:52:50 +00:00
'entity_type' => $instance [ 'entity_type' ],
2009-02-05 03:42:58 +00:00
'bundle' => $instance [ 'bundle' ],
'data' => $data ,
'deleted' => $instance [ 'deleted' ],
);
// We need to tell drupal_update_record() the primary keys to trigger an
// update.
2009-03-10 09:45:32 +00:00
if ( $update ) {
$record [ 'id' ] = $instance [ 'id' ];
2012-09-27 03:47:21 +00:00
drupal_write_record ( 'field_config_instance' , $record , array ( 'id' ));
2009-05-20 09:48:47 +00:00
}
else {
2012-09-27 03:47:21 +00:00
drupal_write_record ( 'field_config_instance' , $record );
$instance [ 'id' ] = $record [ 'id' ];
2009-03-10 09:45:32 +00:00
}
2009-02-05 03:42:58 +00:00
}
/**
2011-02-19 01:09:31 +00:00
* Reads a single instance record from the database .
2009-12-03 02:30:18 +00:00
*
2011-02-19 01:09:31 +00:00
* Generally , you should use field_info_instance () instead , as it
* provides caching and allows other modules the opportunity to
* append additional formatters , widgets , and other information .
2009-05-28 10:05:32 +00:00
*
2010-02-11 17:44:47 +00:00
* @ param $entity_type
2010-02-12 05:38:10 +00:00
* The type of entity to which the field is bound .
2009-02-05 03:42:58 +00:00
* @ param $field_name
* The field name to read .
* @ param $bundle
* The bundle to which the field is bound .
* @ param array $include_additional
* The default behavior of this function is to not return an instance that
2009-10-01 19:16:57 +00:00
* has been deleted , or whose field is inactive . Setting
* $include_additional [ 'include_inactive' ] or
* $include_additional [ 'include_deleted' ] to TRUE will override this
2009-02-05 03:42:58 +00:00
* behavior .
* @ return
* An instance structure , or FALSE .
*/
2010-02-11 17:44:47 +00:00
function field_read_instance ( $entity_type , $field_name , $bundle , $include_additional = array ()) {
2010-03-27 05:52:50 +00:00
$instances = field_read_instances ( array ( 'entity_type' => $entity_type , 'field_name' => $field_name , 'bundle' => $bundle ), $include_additional );
2009-02-05 03:42:58 +00:00
return $instances ? current ( $instances ) : FALSE ;
}
/**
2009-12-03 02:30:18 +00:00
* Reads in field instances that match an array of conditions .
2009-02-05 03:42:58 +00:00
*
* @ param $param
* An array of properties to use in selecting a field
* instance . Valid keys include any column of the
2009-02-10 03:16:15 +00:00
* field_config_instance table . If NULL , all instances will be returned .
2009-02-05 03:42:58 +00:00
* @ param $include_additional
* The default behavior of this function is to not return field
2009-10-01 19:16:57 +00:00
* instances that have been marked deleted , or whose field is inactive .
* Setting $include_additional [ 'include_inactive' ] or
2009-02-05 03:42:58 +00:00
* $include_additional [ 'include_deleted' ] to TRUE will override this
* behavior .
* @ return
* An array of instances matching the arguments .
*/
function field_read_instances ( $params = array (), $include_additional = array ()) {
2010-02-07 05:12:35 +00:00
$include_inactive = isset ( $include_additional [ 'include_inactive' ]) && $include_additional [ 'include_inactive' ];
$include_deleted = isset ( $include_additional [ 'include_deleted' ]) && $include_additional [ 'include_deleted' ];
2009-02-05 03:42:58 +00:00
$query = db_select ( 'field_config_instance' , 'fci' , array ( 'fetch' => PDO :: FETCH_ASSOC ));
2009-03-10 09:45:32 +00:00
$query -> join ( 'field_config' , 'fc' , 'fc.id = fci.field_id' );
2009-02-05 03:42:58 +00:00
$query -> fields ( 'fci' );
// Turn the conditions into a query.
foreach ( $params as $key => $value ) {
$query -> condition ( 'fci.' . $key , $value );
}
2010-02-07 05:12:35 +00:00
if ( ! $include_inactive ) {
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
$query
-> condition ( 'fc.active' , 1 )
2009-10-01 19:16:57 +00:00
-> condition ( 'fc.storage_active' , 1 );
2009-02-05 03:42:58 +00:00
}
2010-02-07 05:12:35 +00:00
if ( ! $include_deleted ) {
2009-02-05 03:42:58 +00:00
$query -> condition ( 'fc.deleted' , 0 );
$query -> condition ( 'fci.deleted' , 0 );
}
$instances = array ();
$results = $query -> execute ();
foreach ( $results as $record ) {
2010-02-12 05:38:10 +00:00
// Filter out instances on unknown entity types (for instance because the
2010-02-07 05:12:35 +00:00
// module exposing them was disabled).
2010-03-27 05:52:50 +00:00
$entity_info = entity_get_info ( $record [ 'entity_type' ]);
2010-02-07 05:12:35 +00:00
if ( $include_inactive || $entity_info ) {
$instance = unserialize ( $record [ 'data' ]);
$instance [ 'id' ] = $record [ 'id' ];
$instance [ 'field_id' ] = $record [ 'field_id' ];
$instance [ 'field_name' ] = $record [ 'field_name' ];
2010-03-27 05:52:50 +00:00
$instance [ 'entity_type' ] = $record [ 'entity_type' ];
2010-02-07 05:12:35 +00:00
$instance [ 'bundle' ] = $record [ 'bundle' ];
$instance [ 'deleted' ] = $record [ 'deleted' ];
module_invoke_all ( 'field_read_instance' , $instance );
$instances [] = $instance ;
}
2009-02-05 03:42:58 +00:00
}
return $instances ;
}
/**
2009-12-03 02:30:18 +00:00
* Marks a field instance and its data for deletion .
2009-02-05 03:42:58 +00:00
*
2009-10-02 14:39:43 +00:00
* @ param $instance
* An instance structure .
2010-12-15 04:13:48 +00:00
* @ param $field_cleanup
* If TRUE , the field will be deleted as well if its last instance is being
2011-09-24 20:44:06 +00:00
* deleted . If FALSE , it is the caller ' s responsibility to handle the case of
2010-12-15 04:13:48 +00:00
* fields left without instances . Defaults to TRUE .
2009-02-05 03:42:58 +00:00
*/
2010-12-15 04:13:48 +00:00
function field_delete_instance ( $instance , $field_cleanup = TRUE ) {
2009-02-05 03:42:58 +00:00
// Mark the field instance for deletion.
db_update ( 'field_config_instance' )
-> fields ( array ( 'deleted' => 1 ))
2009-10-02 14:39:43 +00:00
-> condition ( 'field_name' , $instance [ 'field_name' ])
2010-03-27 05:52:50 +00:00
-> condition ( 'entity_type' , $instance [ 'entity_type' ])
2009-10-02 14:39:43 +00:00
-> condition ( 'bundle' , $instance [ 'bundle' ])
2009-02-05 03:42:58 +00:00
-> execute ();
2010-12-15 04:13:48 +00:00
// Clear the cache.
field_cache_clear ();
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
// Mark instance data for deletion.
2009-10-02 14:39:43 +00:00
$field = field_info_field ( $instance [ 'field_name' ]);
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
module_invoke ( $field [ 'storage' ][ 'module' ], 'field_storage_delete_instance' , $instance );
2010-12-15 04:13:48 +00:00
// Let modules react to the deletion of the instance.
2009-09-09 11:37:34 +00:00
module_invoke_all ( 'field_delete_instance' , $instance );
2010-12-15 04:13:48 +00:00
// Delete the field itself if we just deleted its last instance.
if ( $field_cleanup && count ( $field [ 'bundles' ]) == 0 ) {
field_delete_field ( $field [ 'field_name' ]);
}
2009-02-05 03:42:58 +00:00
}
/**
* @ } End of " defgroup field_crud " .
2009-02-08 21:22:59 +00:00
*/
2009-08-11 14:59:40 +00:00
2009-12-03 02:30:18 +00:00
/**
2009-08-11 14:59:40 +00:00
* @ defgroup field_purge Field API bulk data deletion
* @ {
* Clean up after Field API bulk deletion operations .
*
* Field API provides functions for deleting data attached to individual
2010-02-12 05:38:10 +00:00
* entities as well as deleting entire fields or field instances in a single
2009-08-11 14:59:40 +00:00
* operation .
*
2010-02-12 05:38:10 +00:00
* Deleting field data items for an entity with field_attach_delete () involves
2009-08-11 14:59:40 +00:00
* three separate operations :
* - Invoking the Field Type API hook_field_delete () for each field on the
2010-02-12 05:38:10 +00:00
* entity . The hook for each field type receives the entity and the specific
2009-08-11 14:59:40 +00:00
* field being deleted . A file field module might use this hook to delete
* uploaded files from the filesystem .
* - Invoking the Field Storage API hook_field_storage_delete () to remove
* data from the primary field storage . The hook implementation receives the
2010-02-12 05:38:10 +00:00
* entity being deleted and deletes data for all of the entity 's bundle' s
2009-08-11 14:59:40 +00:00
* fields .
* - Invoking the global Field Attach API hook_field_attach_delete () for all
2010-02-12 05:38:10 +00:00
* modules that implement it . Each hook implementation receives the entity
* being deleted and can operate on whichever subset of the entity 's bundle' s
2009-08-11 14:59:40 +00:00
* fields it chooses to .
*
* These hooks are invoked immediately when field_attach_delete () is
* called . Similar operations are performed for field_attach_delete_revision () .
*
* When a field , bundle , or field instance is deleted , it is not practical to
2010-02-12 05:38:10 +00:00
* invoke these hooks immediately on every affected entity in a single page
2009-08-11 14:59:40 +00:00
* request ; there could be thousands or millions of them . Instead , the
* appropriate field data items , instances , and / or fields are marked as deleted
* so that subsequent load or query operations will not return them . Later , a
* separate process cleans up , or " purges " , the marked - as - deleted data by going
* through the three - step process described above and , finally , removing
* deleted field and instance records .
*
* Purging field data is made somewhat tricky by the fact that , while
2010-02-12 05:38:10 +00:00
* field_attach_delete () has a complete entity to pass to the various deletion
2009-08-11 14:59:40 +00:00
* hooks , the Field API purge process only has the field data it has previously
2010-02-12 05:38:10 +00:00
* stored . It cannot reconstruct complete original entities to pass to the
* deletion hooks . It is even possible that the original entity to which some
2009-08-11 14:59:40 +00:00
* Field API data was attached has been itself deleted before the field purge
* operation takes place .
*
2010-02-12 05:38:10 +00:00
* Field API resolves this problem by using " pseudo-entities " during purge
* operations . A pseudo - entity contains only the information from the original
* entity that Field API knows about : entity type , id , revision id , and
2009-08-11 14:59:40 +00:00
* bundle . It also contains the field data for whichever field instance is
* currently being purged . For example , suppose that the node type 'story' used
* to contain a field called 'subtitle' but the field was deleted . If node 37
2010-02-12 05:38:10 +00:00
* was a story with a subtitle , the pseudo - entity passed to the purge hooks
2009-08-11 14:59:40 +00:00
* would look something like this :
*
* @ code
2010-02-12 05:38:10 +00:00
* $entity = stdClass Object (
2009-08-11 14:59:40 +00:00
* [ nid ] => 37 ,
* [ vid ] => 37 ,
* [ type ] => 'story' ,
* [ subtitle ] => array (
* [ 0 ] => array (
* 'value' => 'subtitle text' ,
* ),
* ),
* );
* @ endcode
2011-11-30 02:42:42 +00:00
*
2011-12-22 09:32:53 +00:00
* See @ link field Field API @ endlink for information about the other parts of
* the Field API .
2009-08-11 14:59:40 +00:00
*/
/**
2009-12-03 02:30:18 +00:00
* Purges a batch of deleted Field API data , instances , or fields .
2009-08-11 14:59:40 +00:00
*
2012-03-23 19:45:06 +00:00
* This function will purge deleted field data in batches . The batch size
* is defined as an argument to the function , and once each batch is finished ,
* it continues with the next batch until all have completed . If a deleted field
* instance with no remaining data records is found , the instance itself will
* be purged . If a deleted field with no remaining field instances is found , the
* field itself will be purged .
2009-08-11 14:59:40 +00:00
*
* @ param $batch_size
* The maximum number of field data records to purge before returning .
*/
function field_purge_batch ( $batch_size ) {
// Retrieve all deleted field instances. We cannot use field_info_instances()
// because that function does not return deleted instances.
$instances = field_read_instances ( array ( 'deleted' => 1 ), array ( 'include_deleted' => 1 ));
foreach ( $instances as $instance ) {
2010-06-14 15:41:03 +00:00
// field_purge_data() will need the field array.
2009-08-11 14:59:40 +00:00
$field = field_info_field_by_id ( $instance [ 'field_id' ]);
2010-06-14 15:41:03 +00:00
// Retrieve some entities.
2010-06-17 13:16:57 +00:00
$query = new EntityFieldQuery ();
2010-06-14 15:41:03 +00:00
$results = $query
-> fieldCondition ( $field )
-> entityCondition ( 'bundle' , $instance [ 'bundle' ])
-> deleted ( TRUE )
-> range ( 0 , $batch_size )
-> execute ();
2009-08-11 14:59:40 +00:00
2010-06-14 15:41:03 +00:00
if ( $results ) {
2012-08-07 19:22:09 +00:00
foreach ( $results as $entity_type => $ids_array ) {
$entities = array ();
foreach ( $ids_array as $ids ) {
$entities [ $ids -> entity_id ] = _field_create_entity_from_ids ( $ids );
}
field_attach_load ( $entity_type , $entities , FIELD_LOAD_CURRENT , array ( 'field_id' => $field [ 'id' ], 'deleted' => 1 ));
foreach ( $entities as $entity ) {
2010-02-12 05:38:10 +00:00
// Purge the data for the entity.
2012-08-07 19:22:09 +00:00
field_purge_data ( $entity_type , $entity , $field , $instance );
2009-08-11 14:59:40 +00:00
}
}
}
else {
// No field data remains for the instance, so we can remove it.
field_purge_instance ( $instance );
}
}
2010-12-15 04:13:48 +00:00
// Retrieve all deleted fields. Any that have no instances can be purged.
2009-08-11 14:59:40 +00:00
$fields = field_read_fields ( array ( 'deleted' => 1 ), array ( 'include_deleted' => 1 ));
foreach ( $fields as $field ) {
2010-12-15 04:13:48 +00:00
$instances = field_read_instances ( array ( 'field_id' => $field [ 'id' ]), array ( 'include_deleted' => 1 ));
if ( empty ( $instances )) {
2009-08-11 14:59:40 +00:00
field_purge_field ( $field );
}
}
}
/**
2010-02-12 05:38:10 +00:00
* Purges the field data for a single field on a single pseudo - entity .
2009-08-11 14:59:40 +00:00
*
* This is basically the same as field_attach_delete () except it only applies
2010-02-12 05:38:10 +00:00
* to a single field . The entity itself is not being deleted , and it is quite
2009-08-11 14:59:40 +00:00
* possible that other field data will remain attached to it .
*
2010-02-11 17:44:47 +00:00
* @ param $entity_type
* The type of $entity ; e . g . 'node' or 'user' .
* @ param $entity
2010-04-24 07:19:09 +00:00
* The pseudo - entity whose field data is being purged .
2009-08-11 14:59:40 +00:00
* @ param $field
* The ( possibly deleted ) field whose data is being purged .
* @ param $instance
* The deleted field instance whose data is being purged .
*/
2010-02-11 17:44:47 +00:00
function field_purge_data ( $entity_type , $entity , $field , $instance ) {
2009-08-11 14:59:40 +00:00
// Each field type's hook_field_delete() only expects to operate on a single
// field at a time, so we can use it as-is for purging.
$options = array ( 'field_id' => $instance [ 'field_id' ], 'deleted' => TRUE );
2010-02-11 17:44:47 +00:00
_field_invoke ( 'delete' , $entity_type , $entity , $dummy , $dummy , $options );
2009-08-11 14:59:40 +00:00
// Tell the field storage system to purge the data.
2010-02-11 17:44:47 +00:00
module_invoke ( $field [ 'storage' ][ 'module' ], 'field_storage_purge' , $entity_type , $entity , $field , $instance );
2009-08-11 14:59:40 +00:00
// Let other modules act on purging the data.
foreach ( module_implements ( 'field_attach_purge' ) as $module ) {
$function = $module . '_field_attach_purge' ;
2010-02-11 17:44:47 +00:00
$function ( $entity_type , $entity , $field , $instance );
2009-08-11 14:59:40 +00:00
}
}
/**
2009-12-03 02:30:18 +00:00
* Purges a field instance record from the database .
2009-08-11 14:59:40 +00:00
*
* This function assumes all data for the instance has already been purged , and
* should only be called by field_purge_batch () .
*
* @ param $instance
* The instance record to purge .
*/
function field_purge_instance ( $instance ) {
db_delete ( 'field_config_instance' )
-> condition ( 'id' , $instance [ 'id' ])
-> execute ();
// Notify the storage engine.
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
$field = field_info_field_by_id ( $instance [ 'field_id' ]);
module_invoke ( $field [ 'storage' ][ 'module' ], 'field_storage_purge_instance' , $instance );
2009-08-11 14:59:40 +00:00
// Clear the cache.
2009-09-07 15:49:01 +00:00
field_info_cache_clear ();
2009-08-11 14:59:40 +00:00
// Invoke external hooks after the cache is cleared for API consistency.
module_invoke_all ( 'field_purge_instance' , $instance );
}
/**
2009-12-03 02:30:18 +00:00
* Purges a field record from the database .
2009-08-11 14:59:40 +00:00
*
* This function assumes all instances for the field has already been purged ,
* and should only be called by field_purge_batch () .
*
* @ param $field
* The field record to purge .
*/
function field_purge_field ( $field ) {
$instances = field_read_instances ( array ( 'field_id' => $field [ 'id' ]), array ( 'include_deleted' => 1 ));
if ( count ( $instances ) > 0 ) {
2010-06-05 12:05:25 +00:00
throw new FieldException ( t ( 'Attempt to purge a field @field_name that still has instances.' , array ( '@field_name' => $field [ 'field_name' ])));
2009-08-11 14:59:40 +00:00
}
db_delete ( 'field_config' )
-> condition ( 'id' , $field [ 'id' ])
-> execute ();
// Notify the storage engine.
- Patch #443422 by yched, bjaspan | chx, merlinofchaos, Scott Reynolds, 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.
2009-09-27 12:52:55 +00:00
module_invoke ( $field [ 'storage' ][ 'module' ], 'field_storage_purge_field' , $field );
2009-08-11 14:59:40 +00:00
// Clear the cache.
2009-09-07 15:49:01 +00:00
field_info_cache_clear ();
2009-08-11 14:59:40 +00:00
// Invoke external hooks after the cache is cleared for API consistency.
module_invoke_all ( 'field_purge_field' , $field );
}
/**
* @ } End of " defgroup field_purge " .
*/