[MIG] event: Migration scripts - #712
Conversation
cubells
commented
Dec 26, 2016
cubells
commented
- Analysis work
- Pre-migration script
- Post-migration script
|
Why have you used 8.0 commits? In this case, you don't have to follow the migration guide: don't import commits corresponding to previous version. |
* Analysis work * Pre-migration script * Post-migration script
1d93bda to
c224ddb
Compare
|
|
||
|
|
||
| event / event.event / event_logo (html) : NEW | ||
| # Noting to do |
| # Nothing to do as country_id is now a related field from address_id | ||
|
|
||
| event / event.event / email_confirmation_id (many2one): DEL relation: email.template | ||
| event / event.event / email_registration_id (many2one): DEL relation: email.template |
There was a problem hiding this comment.
This worries me, as we have customers using specific templates for each event. How Odoo v9 handles this? Anyway, at least we need to keep the columns if an specific module restoring this function comes.
|
|
||
| def update_seats_availability(cr): | ||
| cr.execute(""" | ||
| UPDATE event_event |
There was a problem hiding this comment.
You don't need to indent so much these lines. One indent level more than previous line is enough.
| cr.execute(""" | ||
| UPDATE event_event | ||
| SET seats_availability = 'limited' | ||
| WHERE seats_max IS NOT NULL |
There was a problem hiding this comment.
seats_max is an integer, so the value is NULL or 0 when you don't set it?
| event / event.event / type (many2one) : was renamed to event_type_id [nothing to to] | ||
| # Nothing to do | ||
|
|
||
| event / event.mail / event_id (many2one) : NEW relation: event.event, required: required |
There was a problem hiding this comment.
Is this the replacement of the two dissapeared fields with templates? Without looking the code or runbot, it seems this is a way to program reminders and steps to send emails in certain stages.
There was a problem hiding this comment.
No, it isn't. The field contains the template of the mail that will be automatically sent. It isn't the same that email_confirmation_id and email_registration_id fields.
| event / event.registration / user_id (many2one) : DEL relation: res.users | ||
| # Nothing to do: new relation | ||
|
|
||
| event / event.type / default_email_event (many2one): DEL relation: email.template |
There was a problem hiding this comment.
How do we put now default event.mail?
There was a problem hiding this comment.
It seems this feature don't exist in version 9.0.
|
This is still pending the creation of mail records. |
|
cc @Tecnativa |
|
cc @pedrobaeza |
3 participants
