Upgrade from Alpha5 to Beta2 returns a database error when running update.php

#1555100: Database error upon attempting to enable module

Po3t,

I am trying to install the newer versions of Commerce Registrations and Entity Registrations. Would you be able to share with me what you uninstalled and how you did it, as well as how you installed the newer versions? I am still learning things like Git and I don't have experience altering databases. So any help you can give me would be very much appreciated.

Currently, I have Commerce Registrations 7.x-2.0-alpha5 and Entity Registrations 7.x-1.0-alpha4, and I want to install Commerce Registrations 7.x-2.0-beta1 and Entity Registrations 7.x-1.0-beta2. I have Drupal 7.14 installed.

Also, I have some commerce products that I have enabled for registrations. Do you know if I have to disable all of the registrations for those products? When I tried to disable the older Entity Registration the check box was grayed out because the message said 'Required by: Drupal (Field type(s) in use'. Or is the uninstall and new install process unrelated to that?

Thank you,
Loube

Po3t,

Thank you for your response and help. I now have the old version removed and the newer installed. I have existing products that seem to have carried over to the new version.

Hi guys,

I had the same problem going to Beta1. I've modified my registration.install to accommodate an upgrade path as opposed to the defined re-install process that is required for Alpha5 to Beta1+ at the moment.

I'll create a proper patch, but essentially it requires a hook_update_N and we can create the `registration_state` table and add the indexes and column into the `registration` table.

I've added two updates, so that the `registration_state table` is created before adding the column and foreign key reference.

Anyway I may be getting ahead of myself with all this, but I'll post my install patch up and hopefully that'll help? The reason I had to investigate this further is because we have a lot of data in the registration table and so didn't want to risk dropping it all in order to re-create the tables with the adjusted schema. May have been OK, but I like the idea of a clean upgrade path :-)

Oh FYI, happy to open a new issue for the patch and reference this issue.

Thanks,
luke

Hi dpi/Loube/Po3t,

OK I've rolled a patch against registration beta3, have a look and let me know what you think?

It's just for the registration.install, and meaning that the module can be updated from Alpha5 to Beta1/2/3.

Let me know if there is anything wrong with the patch!

Thanks,
luke

registration_uninstall() still needs fixing. Output after patching:

$ drush pm-uninstall registration
The following modules will be uninstalled: registration
Do you really want to continue? (y/n): y
WD php: PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table '_d.d_registration_state' doesn't exist: DELETE[error]
FROM {registration_state} 
WHERE  (name IN  (:db_condition_placeholder_0, :db_condition_placeholder_1, :db_condition_placeholder_2)) ; Array
(
    [:db_condition_placeholder_0] => complete
    [:db_condition_placeholder_1] => pending
    [:db_condition_placeholder_2] => canceled
)
 in registration_uninstall() (line 375 of sites/all/modules/registration/registration.install).
Cannot modify header information - headers already sent by (output started at /usr/share/drush/includes/output.inc:37)                 [warning]
bootstrap.inc:1239
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table '_d.d_registration_state' doesn't exist: DELETE FROM {registration_state} 
WHERE  (name IN  (:db_condition_placeholder_0, :db_condition_placeholder_1, :db_condition_placeholder_2)) ; Array
(
    [:db_condition_placeholder_0] => complete
    [:db_condition_placeholder_1] => pending
    [:db_condition_placeholder_2] => canceled
)
 в registration_uninstall() (рядок 375 із sites/all/modules/registration/registration.install).
Drush command terminated abnormally due to an unrecoverable error.                                                                     [error]

I've added the
if (db_table_exists('registration_state')) {
condition.

A proper way to go about it would be to not bother deleting the row entries in the states table, as the states table is provided by registration_schema(), and is automatically deleted by Drupal upon uninstall, prior to running hook_uninstall (hence the uninstall error).

Just to be clear, the patch does not have it. It's already in Registration. Commit #f36156c4.

hook_uninstall does not need to delete rows if the table is being dropped by Drupal.

Hi all,

So my patch was more aimed towards an upgrade path and not an uninstall/re-install process, hence why I wasn't checking for a registration_state table existence in uninstall.

Also if it's in beta3 already then that's cool, as my update was from alpha5 > beta1. So we could merge my hook_update_N's with the beta3 install file ready for beta4?

thanks,
luke

Sorry I did suggest that you could update to Beta3 in #9, my bad as I hadn't tested that yet, just Beta1.

thanks,
luke

Gang - Not sure what the goal of this ticket is, but the patch as stands empties the hook_install() function which is a non-starter. We've stated clearly from day one that there will be no upgrade path from alpha. If the community works to create an upgrade patch, that's obviously great if folks find it useful, but we're not going to commit to the module. Thanks for understanding and let us know what we can to help anyone who's still stuck in alpha land.

Morning levelos,

OK no worries, yes my patch was always intended as an upgrade path for those moving from Alpha05 > Beta01.

But I've re-rolled and added the hook_install back in. It can live on this thread for anyone who wants to use it if that's OK?

Thanks and love the module btw!
luke

@luketsimmons - Thanks for the patch and I certainly didn't imply that it can't live on! I hope folks find it helpful. I also don't want to keep the ticket active implying work still needs to be done here. Is there a better solution? Perhaps a handbook page dedicated to RedHen recipes would be helpful? If so, we can set that and move this over.