I encountered a bug where the cloned tables that are generated (for CCK generated tables) have a different column ordering than what's in the original database.

It wouldn't be so bad, but the data is imported with the original column ordering, so the wrong data ends up in the wrong columns.

The column ordering (after the vid and nid columns) doesn't appear to be in alphabetical, on the fieldname, nor inversed from the original ordering, nor ordered be field weight.

It makes all tests that check values on that node type fail.

Is there a DB schema cache or something that needs to get reset or something?

CommentFileSizeAuthor
2010-10-19_05.54.04.jpg111.58 KBrich.yumul

Comments

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented

Interesting. Since db fields are added to the original tables in the order that CCK fields are added to the node type, this makes sense. The fix will be to change the code to explicitly name the db columns on insert.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented

This has been fixed by explicitly naming fields in the insert statement.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.