Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Reported by schema.module:
column notified - differences on: size, unsigned
declared: array('description' => 'TODO: please describe this field!', 'type' => 'int', 'size' => 'tiny', 'not null' => TRUE, 'default' => 0)
actual: array('description' => 'TODO: please describe this field!', 'type' => 'int', 'unsigned' => TRUE, 'size' => 'small', 'not null' => TRUE, 'default' => 0)
Comment | File | Size | Author |
---|---|---|---|
#10 | comment_notify-schema_mismatch-1279470-9.patch | 965 bytes | iamEAP |
Comments
Comment #1
gregglesWas this a fresh install? An upgrade?
Comment #2
Wim LeersFresh install of comment_notify, after a Drupal core upgrade from D5. I'm pretty sure I have upgraded comment_notify from 1.0-beta2 to 1.0-rc1, but I'm not 100% certain. (Local dev site.)
Comment #3
gregglesOk, thanks.
Comment #4
nikhiljain CreditAttribution: nikhiljain commentedI'm having this problem in 6.x-1.6 version.
Comment #5
nikhiljain CreditAttribution: nikhiljain commentedany solution yet?
Comment #6
gregglesAfaik this isn't a "problem" aside from schema complaining about it so it's not a priority to me. I'd be happy to review/commit a patch someone else creates.
Comment #7
nikhiljain CreditAttribution: nikhiljain commentedI'm sorry for I'm not a drupal developer. So cant provide a patch. I'll wait for the next release then. But just to be clear, can this schema mismatch issue affect my site in any sense?
Comment #8
jasonsbytes CreditAttribution: jasonsbytes commentedThe module creates/updates the notified database field as type: unsigned small however the schema declaration for this field in the module is set to type: signed tiny.
Since this field appears to be a 1 or 0 flag, I changed the datatype using phpMyAdmin on the notified field and set it to tinyint and removed the unsigned attribute and that eliminated the schema complaint.
Comment #10
iamEAP CreditAttribution: iamEAP commentedRan into this on a D6 -> D7 upgrade.
Looks like the patch here included an update that didn't correspond to the schema: #639618: user warning: Field 'notified' doesn't have a default value
Here's a patch that brings the schema back to what's declared.
Note this patch shouldn't have any effect on the issue referenced above, as it was about a missing default value, which is in the schema now.
Comment #11
gregglesGreat, fixed http://drupalcode.org/project/comment_notify.git/commit/d6aacfb
Thanks for your help, iamEAP, jasonbytes,
Comment #13
Wim LeersHurray! :)