* Betr.: " Re: [tryton-dev] Some issues when implementing triggers" (Mon, 24 May 2010 14:02:54 +0200):
> On 24/05/10 13:40 +0200, Mathias Behrle wrote:
> > * Betr.: " Re: [tryton-dev] Some issues when implementing triggers" (Mon, 24
> > May 2010 08:54:19 +0200):
> >
> > > On 23/05/10 13:34 +0200, Mathias Behrle wrote:
> > > > * Betr.: " [tryton-dev] Some issues when implementing triggers" (Sat,
> > > > 22 May 2010 13:13:57 +0200):
> > > >
> > > > > * Wrong required field added to res.user:
> > > > >
> > > > > The module dashboard add a Selection field 'dashboard_layout' that is
> > > > > required. So this is wrong and I will fix the module but there is
> > > > > still a migration issue because the creation of a user before the
> > > > > load of this module will fail. So I propose to duplicate the
> > > > > migration script of this field from dashboard module into res module.
> > > > > This will ensure that the field will no more be required at the early
> > > > > stage.
> > > >
> > > > I don't think you will provide such migration in res (resp. server)
> > > > module(s) for other than B2CK modules. So for me this is not the right
> > > > way, but there should be 'Release Notes' for releases indicating the
> > > > problem and its resolution.
> > >
> > > If we don't migration doesn't work out-of-the-box.
> >
> > You could use the Administrator as user for Run On Time Triggers, move the
> > migration into the respective modules,
>
> I can't because cron in multi-company environment change the company of the
> user for each companies. So we can not change the admin company like that.
Another alternative: you could create the user in code instead of xml with the
possibility to check, if the creation of the user is possible (of course not
being part of the system configuration).
OTOH: I like the idea that you are giving up the strict separation between
modules and framework, thus moving more from framework to business application.
So just go for it...;)
> > and add a separate user Cron Trigger
> > later when upgrading from 1.8 to 2.0. Since you considered anyway to extend
> > the modules to have those access permissions (like admin has) there would
> > be no problem from this point of view.
>
> Postpone problem will not solve it. We profide migration from any previous
> release not only the previous one.
So you would have to wait until support for 1.6 is dropped.
--
Mathias Behrle
MBSolutions
Gilgenmatten 10 A
D-79114 Freiburg
Tel: +49(761)471023
Fax: +49(761)4770816
http://mbsolutions.selfip.biz
UStIdNr: DE 142009020
PGP/GnuPG key availabable from any keyserver, ID: 0x89BCA161
signature.asc
Description: PGP signature
