When using the Schema module, it is reporting an error that the schema is defined, but the table does not exist.

CommentFileSizeAuthor
#1 943408-imageapi_text-primary-key.patch586 bytesmrfelton

Comments

mrfelton’s picture

mrfelton commented
StatusFileSize
new 943408-imageapi_text-primary-key.patch586 bytes

Attached patch removed the annoying warning 'The export definition of imageapi_text_style is missing the "primary key" property.'

dman’s picture

dman commented
Status: Active » Fixed

Yeah, that's a bit of a cheat going on there.
I'm experimenting with ctools 'exportables'. For ctools exportables to auto-load the data, it relies on a "schema" being present in the install file in order to know what to save.
HOWEVER, I'm not really using any database storage to save the various presets - it's all just in the variables table. My expectation is that there will only be between 1-5 text presets in use on any one site, and doing a whole database layer just for that is unneccessary. So I use the variables table, but pretend it's database data.
There may be ways around it to get ctools to understand what I'm doing, but I'm still new to ctools. There are probably cleaner ways, I'm just going from example code at the moment

Your suggested fix is safe and makes sense, I'll put it into the -dev now!
http://drupal.org/cvs?commit=437162

Status: Fixed » Closed (fixed)

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