Obsolete fields on migrated data objects throw error

Question

Obsolete fields on migrated data objects throw error

Closed this issue 10 years ago · 4 comments

I have noticed that if the database table has some obsolete fields no longer in your data object class then attempting to publish for the first time results in an error.

This could of course be a Silverstripe issue, I am using 3.1.6.

Answer 1 · 2014-10-15T15:06:11.000Z

I can easily reproduce by adding a new column in the database to the unprefixed table. To stop the error the _version prefixed table needs the same column.

Answer 2 · 2014-10-15T17:21:52.000Z

@stecman, want to have a look at this?

Answer 3 · 2014-10-15T21:13:37.000Z

There's an issue on SilverStripe that I think resembles what is being described.

Versioned not ignoring obsolete fields: silverstripe/silverstripe-framework#2610

Might be helpful

Answer 4 · 2014-10-15T21:19:50.000Z

Good find! Sounds exactly like this issue.