Curiosity satisfied, thanks :)
2009/9/23 Ismael Ciordia, Openbravo <[email protected]>
> Rafa,
>
> if you look at the old implementation, the method to update used entries in
> ad_text_interfaces uses an ugly (and wrong) sql -> min ad_text_interface_id
> from the union of candidates: that text in that module for that file, that
> text in that module without a specific file, that text in other
> indevelopment module for that file, that text in other indevelopment module
> without a specific file.
>
> As a result, when there is an entry in ad_text_interfaces that is specific
> for a file and there is another entry with the same text, generic for all
> files and smaller id that entry was not marked as used (I realize the
> explanation is tricky, but it is what it is :-)
>
> Antonio's refactoring is just proper implementation of that sql: first
> updates an entry with that text in that module for that file, if no entry is
> updated then updates an entry for that text in that module without a
> specific file, and so on.
>
> Hope it satisfies your curiosity :-)
>
> Ismael
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-development
