Bug #8883
ensure FWD data import always creates indexes even if no dump file exists for a table
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
Related issues
History
#1 Updated by Constantin Asofiei 16 days ago
- Related to Bug #7924: add support for creating an empty database added
#2 Updated by Constantin Asofiei 16 days ago
If there is no data dump file for a table, FWD import process should re-index that table; currently only tables which have a non-zero size .d file are processed and have the indexes created automatically.
This is confusing, as one could expect for the import process to leave the database in a 'fully prepared' state, without having to run manually the index DDLs.