The {field_config} table has a dedicated 'cardinality' column, but the cardinality also ends up in the serialized 'data' column.

Attached patch removes cardinality from 'data' - although I think at some point long ago we raised the question of which properties deserved actual columns vs. going in the 'data'. Answer was "the properties you'd need in the WHERE section when using field_read_fields() or field_read_instances()".
I'm not sure cardinality fits this definition...

CommentFileSizeAuthor
field_config_cardinality.patch880 bytesyched

Comments

yched’s picture

yched commented
Status: Active » Needs review
moshe weitzman’s picture

moshe weitzman commented
Status: Needs review » Reviewed & tested by the community

I'm not too fond of the "unset() to prevent saving in data column" pattern that we have here and in users table. But, this patch is just a simple bug fix so RTBC

dries’s picture

dries commented
Status: Reviewed & tested by the community » Fixed

Committed to CVS HEAD. Thanks!

Status: Fixed » Closed (fixed)

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