stray {content_type_} table

Same problem here. I recognized that the table "content_type_" was created after updating to Drupal 5.11 (from 5.10). I had to disable alle contributed modules before update. After update I activated alle modules again. When activating CCK I got the message that tabele "content_type_" was created. Is this normal? Can I delete the table?

@wflorian, this is an issue for Drupal 6, you're reporting seeing it in Drupal 5. But that's interesting, because we assumed it was being created by something in Drupal 6 and maybe it's not.

I have gotten this in the past in D6, but no longer see it using the latest -dev code. I guess we'll have to keep an eye on D5 to see if it is turning up there.

Anyway, it's perfectly safe to delete that table.

Hi Karen,

like I said I just upgraded from Drupal 5.10 to 5.11.
I disabled all none-core modules, switched to Garland theme. Copied all new data from 5.10. Then ran the update.php and finally activated all none-core modules again. After doing this I got the message that table "content_type_" was created.

But anyway thank you for your answer, I will delete the table on a test system first and look if anything happens :)

Regards.
Florian

It's not necessary to do all that for a minor version upgrade, you should have been fine to just add the new 5.11 code and run update.php without disabling modules.

I'll play around with doing it your way to see if I can figure out where this might be coming from.

Hi Karen,

ok good to know, even if I just followed the instructions in upgrade.txt. But I will do it your way, if there will be a new update for D5 in the future.

Would be great if your can figure out why the table was created. I have several other CCK created tables like "content_type_XXX"

I thought maybe the clue here was that something was happening when CCK modules are disabled and re-enabled, but I can't find any way to create that table by just disabling and re-enabling modules. Unless someone comes up with a reliable way to reproduce this behavior, there's nothing more we can do.

So I'll just leave it as an active issue. I saw one of these tables once, too, but have no idea when or how it appeared.

In the meantime, it won't hurt anything and it's perfectly safe to delete the table if it does show up.