2 replaced http://drupal.stackexchange.com/ with https://drupal.stackexchange.com/
source | link

I think that this error is recoverable if you drop the cache_config table because cache tables are created dynamically at run time if they do not exist when using a database backend.

Like BradyBrady suggested there may be a bug in the Drupal installer where that table was not created correctly. To dig more into this bug, if you're interested, you would need to look at the MySQL log to see what happened and try to reproduce it.

I think that this error is recoverable if you drop the cache_config table because cache tables are created dynamically at run time if they do not exist when using a database backend.

Like Brady suggested there may be a bug in the Drupal installer where that table was not created correctly. To dig more into this bug, if you're interested, you would need to look at the MySQL log to see what happened and try to reproduce it.

I think that this error is recoverable if you drop the cache_config table because cache tables are created dynamically at run time if they do not exist when using a database backend.

Like Brady suggested there may be a bug in the Drupal installer where that table was not created correctly. To dig more into this bug, if you're interested, you would need to look at the MySQL log to see what happened and try to reproduce it.

1
source | link

I think that this error is recoverable if you drop the cache_config table because cache tables are created dynamically at run time if they do not exist when using a database backend.

Like Brady suggested there may be a bug in the Drupal installer where that table was not created correctly. To dig more into this bug, if you're interested, you would need to look at the MySQL log to see what happened and try to reproduce it.