Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
I upgraded from D6 to D7. Everything seems to be working, but when using schema module it reports a discrepancy for job scheduled in the database:
created: not in database
Any idea if I can ignore this or how to align the schema to the latest version?
Thanks, J.
Comments
Comment #1
webflo CreditAttribution: webflo commentedThe
created
column was dropped in #1773690: Column 'created' is not added to database when upgrading from D6. Please make sure you updated to the latest release and run all updates.Comment #2
jelo CreditAttribution: jelo commentedSorry, I am not sure that this is fixed. I followed the recommended upgrade path from 6.x-1.0-beta3 to 7.x-2.0-alpha3. Now I have no "created" column in my database, despite the patch that you reference only being applied against the latest dev version. If I understand you correctly, my upgrade to 7.x-2.0-alpha3 should still have had this column in the database which is why the schema mismatch is reported. This suggests to me that something isn't working correctly in the upgrade path.
Given that the column should not be there anyway anymore, I will basically just ignore the reported mismatch...
Thanks, J.