| 7 field.api.php | hook_field_schema($field) |
| 8 field.api.php | hook_field_schema($field) |
Define the Field API schema for a field structure.
This hook MUST be defined in .install for it to be detected during installation and upgrade.
Parameters
$field: A field structure.
Return value
An associative array with the following keys:
- columns: An array of Schema API column specifications, keyed by column name. This specifies what comprises a value for a given field. For example, a value for a number field is simply 'value', while a value for a formatted text field is the combination of 'value' and 'format'. It is recommended to avoid having the column definitions depend on field settings when possible. No assumptions should be made on how storage engines internally use the original column name to structure their storage.
- indexes: (optional) An array of Schema API indexes definitions. Only columns that appear in the 'columns' array are allowed. Those indexes will be used as default indexes. Callers of field_create_field() can specify additional indexes, or, at their own risk, modify the default indexes specified by the field-type module. Some storage engines might not support indexes.
- foreign keys: (optional) An array of Schema API foreign keys definitions.
Related topics
7 functions implement hook_field_schema()
Note: this list is generated by pattern matching, so it may include some functions that are not actually implementations of this hook.
- field_test_field_schema in modules/
field/ tests/ field_test.install - Implements hook_field_schema().
- file_field_schema in modules/
file/ file.install - Implements hook_field_schema().
- image_field_schema in modules/
image/ image.install - Implements hook_field_schema().
- list_field_schema in modules/
field/ modules/ list/ list.install - Implements hook_field_schema().
- number_field_schema in modules/
field/ modules/ number/ number.install - Implements hook_field_schema().
7 invocations of hook_field_schema()
- drupal_get_complete_schema in includes/
bootstrap.inc - Gets the whole database schema.
- drupal_get_schema_unprocessed in includes/
common.inc - Returns the unprocessed and unaltered version of a module's schema.
- field_create_field in modules/
field/ field.crud.inc - Creates a field.
- field_read_fields in modules/
field/ field.crud.inc - Reads in fields that match an array of conditions.
- field_update_7001 in modules/
field/ field.install - Fix fields definitions created during the d6 to d7 upgrade path.
File
- modules/
field/ field.api.php, line 227
Code
function hook_field_schema($field) {
if ($field['type'] == 'text_long') {
$columns = array(
'value' => array(
'type' => 'text',
'size' => 'big',
'not null' => FALSE,
),
);
}
else {
$columns = array(
'value' => array(
'type' => 'varchar',
'length' => $field['settings']['max_length'],
'not null' => FALSE,
),
);
}
$columns += array(
'format' => array(
'type' => 'varchar',
'length' => 255,
'not null' => FALSE,
),
);
return array(
'columns' => $columns,
'indexes' => array(
'format' => array('format'),
),
'foreign keys' => array(
'format' => array(
'table' => 'filter_format',
'columns' => array('format' => 'format'),
),
),
);
}
Comments
Uninstall
PermalinkOn Converting 6.x modules to 7.x - Categorical:
Database schema (un)installed automatically.
I would assume the same applies for this hook, but please correct me if I'm wrong.
is there a hook_field_schema_alter()?
PermalinkIs there an equivalent of hook_schema_alter() for hook_field_schema()? How does one go about altering a core module field schema (e.g. image module) in contrib space? Guidance would be much appreciated.
look at this
Permalinklook at this http://drupal.org/node/691932#comment-5371474
in what table is this stored?
Permalinkin what table is this stored?
Schemas define tables
PermalinkYour shema definition results in new tables for your module to use rather than working with the tables that support drupal's core.
This schema cannot depend on any field settings
PermalinkBecause field_create_field() is called before the user can edit any settings in the Field UI, and because field_create_field() is the function that leads to this call, this means that any "settings" in the $field array are the defaults provided by hook_field_info() and not user-customized settings.
So only use the information in $field to vary your schema based on constant things like the field type, like text_field_schema() does.