PDOException in latest dev. Fatal error.

-dev is considered unstable at this time.

#1512498: Missing db update for mail and uid column changes

Just want to add that while not ready for production dev is fairly stable. But there is no upgrade path until beta, which is why you're having an error.

I got the same issue but for the alpha, not dev. I used the auto updating feature and afterwards got this exact error. I'm looking to roll back now.

There is still no upgrade path.

Stick with alpha4 unless you know what you're doing. Alpha5 should be demoted from recommended.

Agreed. I foolishly did not save a snapshot of the database before updating.
Any quick tips on what needs to be done to be done to get it working?

Otherwise, any tips on rolling back to a previous module version? ... I have a lot of fields tied up in the module already and I'm getting my feet wet in Drupal 7.

Download alpha4: http://drupal.org/node/1482858

There were no database modifications done in alpha5. Which is the reason why you are having issues. Simply drop alpha4 code back into your installation.

I had tried doing that but still got access denied and PHP errors.
I also tried creating a user_id column but that led to access denied pages aplenty.

For posterity: I ended up force reinstalling the module with Devel (Field types in use block module disabling/enabling, uninstall... don't get me started), recreating the relationship type in GUI (I just had to recreate the type with the same name... all my fields were still there), and then go into the entity_registration table in the database and recreate the record for the one registration I had attached to a node from an old backup.

There were still access errors but a quick emptying of caches and rebuilding permissions eventually fixed this.

For the record, the reason I had changed this issue to "Needs review" is the point that was made above: this alpha should not be the recommended version, in my opinion. The recommended version gets broadcasted to the auto updating feature. Yes, I should have backed up my database first, but if auto update informs you on an update you would assume it's not going to result in a critical breakdown, right? Just my two cents...

At any rate, thanks for the responses, @dpi

Do you have any details of the error? Maybe this is a different issue?

Needs review is usually for when you want someone to look at a patch, and triggers the test bots.

I suppose I should have opened a new issue about rolling back the recommended release... not to step on any toes... I'm just some chump who liked the module and started using it. I haven't contributed yet.

The error is the exact same as described in this thread except it happened in alpha5 after updating:

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'user_uid' in 'where clause': SELECT COUNT(*) AS expression FROM (SELECT 1 AS expression FROM {registration} r WHERE (entity_id = :db_condition_placeholder_0) AND (entity_type = :db_condition_placeholder_1) AND (user_uid = :db_condition_placeholder_2) ) subquery; Array ( [:db_condition_placeholder_0] => 4 [:db_condition_placeholder_1] => node [:db_condition_placeholder_2] => 7 ) in registration_is_registered() (line 812 of /home1/spiritt9/public_html/d7/sites/all/modules/registration/registration.module).

The rolling back access problems probably have something to do with variable assignment or changes in the permission structure. Sometimes Drupal DB holds on to little pieces of data and it's hard to flush the system entirely.

I would recommend holding back alpha5 as recommended until it automatically updates the database as well otherwise it seems odd to recommend it as there's nothing in the release notes about this caveat.

Can the maintainers/devs please share their notes on the SQL for the upgrade path as we've upgraded to the latest dev and knowing what needs to be in the database os the last piece of the puzzle. We NEED to implement the latest version as it contains functionality fundamental to our project.

Many thanks in advance,

@Fixdit I added a user_id column to the registration table. This kind of fixed it but then I got all kinds of access issues. It seems like the last piece in the puzzle but I think there are still some variables that don't get updated or some such. Force uninstalling and reinstalling the module with Devel didn't fix these problems until I did it a few times for the alpha4 version. I think it's a good idea to stick with alpha4 for now. Should probably be the recommended release.