Just ran into an issue where a site has almost 3000 variables (wtf, I know), and I'm trying to export them all with strongarm. I created a module just for the variables and I'm hitting and error when I exported about 1800 of them. Looks like drupal core caches the info file as a serialized array in the system table, but with so many entries, it exceeds the size the SQL field can hold. system.info field is a blog by default and can only holt 65K bytes, next larger in drupal is 'blob:big' which should be fine.

I think features should features alter the core table to be 'blob:big' since it relies on the info file to store these values. I know we could do this in a custom module, but does it make sense for features to make this modification standard?

Comments

mpotter’s picture

mpotter CreditAttribution: mpotter commented
Status: Active » Closed (won't fix)

I'd suggest that Features is not the appropriate solution to your problem. Handling 3000 variables is going to be really slow in Features. I recommend creating a module with a hook that sets the variables to the needed values for your site programatically.

There is no way for Features to alter the core table, and in any case, this just isn't something for Features to handle. Whenever somebody reaches these kind of limits they are likely using Features the wrong way or for the wrong task.