Never seen a module completely fail to work simply because the schema already exists. Here's the error (when enabling the module). Worked around the issue by removing the schema from database but this must be a headache for many many people.

>DatabaseSchemaObjectExistsException: Table login_destination already exists. in DatabaseSchema->createTable() (line 657 of /home/test/7home/includes/database/


akashjain132’s picture

Status: Active » Postponed (maintainer needs more info)

Can't replicate this problem, May be module was not uninstall properly that's why this problem occurred, login_destination is a db table define in hook_schema and it will automatically delete while uninstall a module.

plato1123’s picture

Right, make sure install doesn't fail simply because database scheme already exists, as people may have had to restore databases or partial databases to address other issues/problems with their sites.

Thx for gr8 module, best.

ddrozdik’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Can not reproduce either. I guess this could happen in case when module already used before, but was incorrectly uninstalled.
This issue could be closed since the issue is not reproducible.