Additional uncaught exception thrown while handling exception.

Original

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mikerz_minimi.relation_type'

doesn't exist: SELECT rt.predicate AS predicate, rt.label AS label, rt.directional AS directional, rt.transitive AS transitive, rt.min_arity AS min_arity, rt.max_arity AS max_arity FROM {relation_type} rt; Array ( ) in relation_get_types() (line 231 of /home/mikerz/public_html/minimi/sites/all/modules/relation/relation.module).

Additional

PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mikerz_minimi.relation_type' doesn't exist: SELECT rt.predicate AS predicate, rt.label AS label, rt.directional AS directional, rt.transitive AS transitive, rt.min_arity AS min_arity, rt.max_arity AS max_arity FROM {relation_type} rt; Array ( ) in relation_get_types() (line 231 of /home/mikerz/public_html/minimi/sites/all/modules/relation/relation.module).

Any idea what's going on? minimi is a type of node.
The crappy thing about this error is that I need to delete the relation module folder for the site to load again.

Comments

chx’s picture

chx commented
Status: Active » Postponed (maintainer needs more info)

I would really like to know what has happened here... somehow you got into relation_get_types when the module is not yet installed? Huh?

Vogod’s picture

Vogod commented

Same problem!

chx’s picture

chx commented

Still not particularly helpful error description. What are you guys doing?

mikerz’s picture

mikerz commented

Well, I had already installed the module. Didn't do anything fancy, I just set a relation for the minimi type. Worked fine until maybe last week, when I logged in after a few weeks.

I just checked out my log, I didn't do any updates or installs. Cron ran 5/1, and all of a sudden I was getting these data errors.

This is the first error, caused by update.php apparently:
REFERRER http://www.****.com/****/update.php?op=results
MESSAGE PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mikerz_minimi.relation_type' doesn't exist: SELECT rt.predicate AS predicate, rt.label AS label, rt.directional AS directional, rt.transitive AS transitive, rt.min_arity AS min_arity, rt.max_arity AS max_arity FROM {relation_type} rt; Array ( ) in relation_get_types() (line 231 of /home/****/public_html/****/sites/all/modules/relation/relation.module).

Rather mysterious... I'm thinking at this point, I need to fix my data tables and start again. However, I can't have relation installed or there's this fatal error I can't get around. I'm not too experienced with this kind of work, how would I fix my database as if relation had never existed?

naught101’s picture

naught101 commented

Should be enough to delete all the relation* tables in the db and then delete the relation* rows in the system table, as well as any relation field-relation tables: field_*_relation, and field_*_endpoints.

If you're playing with valuable data, make some backups. Relation will probably not be supplying upgrade paths between alpha versions.

naught101’s picture

naught101 commented
Status: Postponed (maintainer needs more info) » Fixed

Assuming this is fixed?

dpi’s picture

dpi
Location Perth, Australia
commented

I can confirm removing the rows for relation in the system table fixes this issue if you have manually deleted the tables for Relation.

Drupal may think that the tables for Relation are installed because the schema number has not changed.

splash112’s picture

splash112 commented

Had the same problem. The table did indeed not exist, I never came close to using it. So ended up delting the whole module + system references and now my site works again.

Jamie Holly’s picture

Jamie Holly commented
Priority: Normal » Major
Status: Fixed » Active

This really isn't "fixed". Older versions had no schema, so if you are updating, the schema is never installed. I suggest doing a hook_update to actually install the schema and that will fix the broken, older installs.

Changing this to major, as anyone who does attempt to update the module will be left with an unusable site.

naught101’s picture

naught101 commented
Priority: Major » Normal
Status: Active » Closed (won't fix)

It's an alpha. We will not be providing upgrade paths between alphas. This module is not intended for anything but testing until the first beta. If you're worried about wasting your time, or messing up data, don't use it.

Jamie Holly’s picture

Jamie Holly commented

Understood. I was more or less responding to your status update at #6 that it was "fixed". Technically it isn't, but the closed (won't fix) makes much more sense.