On Thu, 2005-12-15 at 16:11 -0800, Howard Chu wrote: > Pierangelo Masarati wrote: > > so it's pretty much unfriendly: consumer info is now in a child of the > > global overlay and nothing about that appears any longer in the > > database; I'd really love to have the global "consumer" overlay append > > its children below the appropriate database, but I don't know how to do > > it (I don't think it's possible within the current framework, because > > when the global overlay is processed the database entries do not exist; > > but I'd love to be contradicted).
> I'm missing something, why does the consumer need to be a global overlay? I did it that way because the consistency checks that the frontend applies (have to) occur before database selection and be_<write>() invocation. So a global overlay seemed to be the best place to determine if a write can take place or not. This, of course, results in a duplicated database selection. p. Ing. Pierangelo Masarati Responsabile Open Solution SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: [EMAIL PROTECTED] ------------------------------------------
