constant CONTENT_DB_STORAGE_PER_FIELD in Content Construction Kit (CCK) 7.3
Same name and namespace in other branches
- 5 content.module \CONTENT_DB_STORAGE_PER_FIELD
- 6.3 content.module \CONTENT_DB_STORAGE_PER_FIELD
- 6 content.module \CONTENT_DB_STORAGE_PER_FIELD
- 6.2 content.module \CONTENT_DB_STORAGE_PER_FIELD
@file Code For D6 to D7 field data update.
Modules can implement hook_content_migrate_field_alter(), hook_content_migrate_instance_alter(), and hook_content_migrate_data_record_alter() to make changes to the settings or data as it is migrated.
3 uses of CONTENT_DB_STORAGE_PER_FIELD
- content_migrate_old_table in modules/
content_migrate/ content_migrate.module - Helper function for finding the table name used to store the D6 field data.
- content_migrate_storage_type in modules/
content_migrate/ content_migrate.module - Helper function for finding the type of table used for storing the D6 field data.
- _content_migrate_batch_process_migrate_data in modules/
content_migrate/ includes/ content_migrate.admin.inc - Batch operation callback to migrate data. Copy old table data to new field table.
File
- modules/
content_migrate/ content_migrate.module, line 10 - Code For D6 to D7 field data update.
Code
define('CONTENT_DB_STORAGE_PER_FIELD', 0);