We want to support a general ORM in cards feature as best we can.  It would be nice if we could just use ActiveRecord/Model features directly, for example validations, but Rails features like validations aren't really designed for variations that can be loaded onto the singleton classes as we do for other model extensions that can be specific to Wagn Sets.  That's not so bad since we have a very nice event system that is Set based from the start.  It means moving the validations into events and we don't just get all the standard validation patterns that Rails supports, but that just means a bit more explicit code for those.

So, this is not specific to the account info, but something we might use whenever we want to have "everything in cards".  Say I want to add an ecommerce gem, but I don't want to create a lot of models (external to Wagn, regular tables, not cards).  It seems like there would be significant adapting even with the ORM in cards feature, but this will still do a lot of the adapting from model rows to content in plus cards so the code will be very much the same as with Rails models.

For this specific case, we have already refactored Wagn so that Foo+*account is a card that is directly associated with an external model (User via the Account class).  The migration would simply take each of the fields of the User model that we are keeping (login for example is now redundant) and copy them to the cards:

Should handle:

• allow user creation even if old email was denied
• ?

accounts+tickets for item