public static function UserConsentItem::schema in General Data Protection Regulation 8.2

Same name and namespace in other branches

1. 8 modules/gdpr_consent/src/Plugin/Field/FieldType/UserConsentItem.php \Drupal\gdpr_consent\Plugin\Field\FieldType\UserConsentItem::schema()
2. 3.0.x modules/gdpr_consent/src/Plugin/Field/FieldType/UserConsentItem.php \Drupal\gdpr_consent\Plugin\Field\FieldType\UserConsentItem::schema()

Returns the schema for the field.

This method is static because the field schema information is needed on creation of the field. FieldItemInterface objects instantiated at that time are not reliable as field settings might be missing.

Computed fields having no schema should return an empty array.

Parameters

\Drupal\Core\Field\FieldStorageDefinitionInterface $field_definition: The field definition.

Return value

array An empty array if there is no schema, or an associative array with the following key/value pairs:

• columns: An array of Schema API column specifications, keyed by column name. The columns need to be a subset of the properties defined in propertyDefinitions(). The 'not null' property is ignored if present, as it is determined automatically by the storage controller depending on the table layout and the property definitions. 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.
• unique keys: (optional) An array of Schema API unique key definitions. Only columns that appear in the 'columns' array are allowed.
• indexes: (optional) An array of Schema API index definitions. Only columns that appear in the 'columns' array are allowed. Those indexes will be used as default indexes. Field definitions 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 key definitions. Note, however, that the field data is not necessarily stored in SQL. Also, the possible usage is limited, as you cannot specify another field as related, only existing SQL tables, such as {taxonomy_term_data}.

Overrides FieldItemInterface::schema

File

modules/gdpr_consent/src/Plugin/Field/FieldType/UserConsentItem.php, line 139

Class

UserConsentItem

Plugin implementation of the 'gdpr_user_consent' field type.

Namespace

Drupal\gdpr_consent\Plugin\Field\FieldType

Code

public static function schema(FieldStorageDefinitionInterface $field_definition) {
  $schema = [
    'indexes' => [
      'target_id' => [
        'target_id',
      ],
    ],
  ];
  $schema['columns']['target_id'] = [
    'description' => 'The ID of the target entity.',
    'type' => 'int',
    'unsigned' => TRUE,
  ];
  $schema['columns']['target_revision_id'] = [
    'description' => 'The Revision ID of the target entity.',
    'type' => 'int',
  ];
  $schema['columns']['agreed'] = [
    'description' => 'Whether the user has agreed.',
    'type' => 'int',
    'size' => 'tiny',
    'default' => 0,
  ];
  $schema['columns']['user_id'] = [
    'description' => 'ID of the user who has accepted.',
    'type' => 'int',
  ];
  $schema['columns']['date'] = [
    'description' => 'Time that the user agreed.',
    'type' => 'varchar',
    'length' => 20,
  ];
  $schema['columns']['user_id_accepted'] = [
    'description' => 'ID of the user who recorded the acceptance',
    'type' => 'int',
  ];
  $schema['columns']['notes'] = [
    'description' => 'Additional notes on the acceptance',
    'type' => 'varchar',
    'length' => '255',
  ];
  return $schema;
}