All, I don't like to execute a process that updates the metadata just before this metadata is going to be commited to the repository (it means that this last change is commited without testing).
Instead I propose to run "synchronize terminology" in validation mode: export.database validates that synchronize terminology will not do any change in metadata. If this validation fails export.database is cancelled and developers get an error and are prompted to run synchronize terminology and test again. Platform team can manage to modify "synchronize terminology" to support this validation mode, it should be a simple change. What do you think? Ismael -----Mensaje original----- De: Pablo Sarobe [mailto:pablo.sar...@openbravo.com] Enviado el: martes, 15 de septiembre de 2009 9:40 Para: openbravo-development@lists.sourceforge.net Asunto: Re: [Openbravo-development] [DB-Consistency-Check]-ERP-pi-pgsql-full > [Still Failing!] It's time to take serious actions and finish with these debates. People has been warning several times about this but the problem persists. If we have to introduce an extra task in order to avoid this problem I vote for that. This problem is coming again and again from the last one year and a half. 30 seconds it's not that much Pablo Juan Pablo Aroztegi escribió: > Hi Antonio, > > In my opinion the most important thing we can do now is to > find out why happens even to experienced developers and solve it once > and for all. Is the system too complex? Is the process too delicate? Is > the process fine but difficult to follow? Does it require a discipline > that is not realistic? If the process fine, easy to follow, but are we > just lazy? > > >> One possible solution to this problem would be to automatically execute >> the Synchronize Terminology process just before the export.database >> task. This would mean that developers wouldn't need to remember to do >> it, but it would add about 30 secs to the overall duration of the >> export.database process. We would need to carefully consider if this is >> worth it. >> > If this fixes most of the inconsistencies then we'll have to consider > it. Some developers may argue that adding a delay to every database > export is unacceptable. And this concern is understandable. What do the > rest think about this? Do you have any alternative idea? > > Thank you for your answer and for your suggestion to fix this. > > > Juan Pablo > > > -------------------------------------------------------------------------- ---- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Openbravo-development mailing list > Openbravo-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openbravo-development > > ---------------------------------------------------------------------------- -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Openbravo-development mailing list Openbravo-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbravo-development ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Openbravo-development mailing list Openbravo-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbravo-development
