Closed (outdated)
Project:
Event
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Aug 2010 at 16:09 UTC
Updated:
13 Apr 2018 at 21:01 UTC
Jump to comment: Most recent
I always have these error message on my admin page:
* Field event_timezones.offset: no Schema type for mysql type time.
* Field event_timezones.offset_dst: no Schema type for mysql type time.
* Field storage_object.md5: no Schema type for mysql type binary.
* Field storage_object.whirlpool: no Schema type for mysql type binary.
Think these errors happened in different installations and worked on this problem a few months ago without result, so I wonder if removing and reinstalling helps...
(I searched this error message in Drupal and there was none; the issue que is to hughe for me to look through all issues if there is another that handles this without mentioning the error message)
Comments
Comment #1
drmtree commentedI also get the following messages on my Open Atrium:
* Field event_timezones.offset: no Schema type for mysql type time.
* Field event_timezones.offset_dst: no Schema type for mysql type time.
Comment #2
ClearXS commentedI use a database prefix, so the error message contains the prefix as well, like "Field 'dbprefixname'event_timezones.offset ..." etc.
To be clear: I use module Schema that reports these database errors/inconsistencies that not necessarily immediately result in system halts or other severe errors. But any minor defect can support in the derailment of the whole system, like an airplane crash when mostly several minor errors & imperfect human response to them come together. Or clogging up the db error list resulting in ignoring the list and more important errors, what then result in a system failure.
http://drupal.org/project/schema
Comment #3
dude4linux commentedI have the same two warning messages at the top of the admin page. I also noted that Schema reports event_timezones as an Extra table.
I accidentally deleted the table while cleaning up a bunch of unused cruft. I think the event module included the event table in the schema API but neglected to include the event_timezones table.
Edit: Additional information. The Schema Inspect shows that the event module defines the schema for the 'event' table, but the 'event_timezones' table is unknown. The following should be added to the event modules schema definition.
Comment #4
lvadillo commentedSpecifically, in what file or files do I need to enter the above code?
Comment #5
ben coleman commentedComment #6
ben coleman commenteddude4linux's schema for event_timezones on postgresql produces the warning:
* Field event_timezones.offset: no Schema type for pgsql type interval.
* Field event_timezones.offset_dst: no Schema type for pgsql type interval.
* event_timezones.offset: no type for Schema type time:normal.
* Field event_timezones.offset: no Schema type for type time.
* event_timezones.offset_dst: no type for Schema type time:normal.
* Field event_timezones.offset_dst: no Schema type for type time.
and event_timezones shows up as a mismatch.
The problem is, of course, that there is no Schema API type for mysql time or pgsql interval. You're not going to totally eliminate Schema warnings until there is a Schema API type for this. The best I can come up so far at least eliminates the mismatch:
lvadillo, this goes in event.install, inside the event_schema function.
Comment #7
japerryEvent for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.