Jump to:
| Project: | Drupal core |
| Version: | 7.0-alpha2 |
| Component: | block.module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
block module
Update #7002
* Failed: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'drupal7.blocks' doesn't existIn that update 7002 the tables are being renamed but it looks my table names are just those ones. So this must be something to upgrade previous version (maybe 6.x drupal or previous 7.x devs).
I suppose a check to know if those databases exists would solve the issue. Something like changing 7002 from:
/**
* Rename {blocks} table to {block}, {blocks_roles} to {block_role} and
* {boxes} to {block_custom}.
*/
function block_update_7002() {
db_rename_table('blocks', 'block');
db_rename_table('blocks_roles', 'block_role');
db_rename_table('boxes', 'block_custom');
}to:
/**
* Rename {blocks} table to {block}, {blocks_roles} to {block_role} and
* {boxes} to {block_custom}.
*/
function block_update_7002() {
if (db_table_exists('blocks')) {
db_rename_table('blocks', 'block');
}
if (db_table_exists('blocks_roles')) {
db_rename_table('blocks_roles', 'block_role');
}
if (db_table_exists('boxes')) {
db_rename_table('boxes', 'block_custom');
}
}If db_rename_table was supposed to deal with that then it is a problem of SCHEMA.API
If I solve that update 7002 with those table existence checks then I get other error on 7004:
block module
Update #7004
* Failed: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'garland-system-help' for key 'tmd'Something related to tmd key.
I suppose some blocks are being inserted with are just in database on alpha1 with same tmd key (theme, module, delta) and then it is violating the unique key constraint. So for and upgrade from alpha1 some of those inserts should be updates (if someting is needed to be updated in upgrade from alpha1) or just not being run if nothing is needed to be changed.
But I don't have enough knowledge of this block module to understand exactly which part of that update_7004 is triggering it.
Maybe this is again triggered by the fact these updates are targetted to previous versions upgrades (6.x or old 7.x-devs)?
Comments
#1
The upgrade path is not supported between alpha versions.
#2
Thanks to clarify I will make a fresh 7.0-alpha2 install as testing 7.x environtment.
Then upgrades are from 6.x versions only? and 7.x updates won't start until first final realease is finished?
#3
7.x to 7.x upgrades will be supported starting at the first beta version. The upgrade path will be guaranteed between beta and RC versions.