Thanks all your suggestions.
I think similarity of the discussed requirements with ordering flow lead to
the suggestions to use Order model. I don't have strong preference to use
one over another as long as we are able to support bulk of the discussed
requirements in this thread in a less
Thanks Deepak,
I'll do also but I feel uncomfortable because I'm unsure of which are used or
not, some are obvious
Also next target is RAT and your related Jira
Jacques
Le 27/10/2017 à 11:16, Deepak Dixit a écrit :
+1 Agreed Jacques,
Same applies for images webapp located at
Hi Paul
Problem with that, it's all or nothing. We only need this for specific use
cases. Having forUpdate in EntityQuery gives us that flexibility. It could be
changed to use either method which depends on the scenario you use it for
Gareth Carter
Software Development Analyst
Stannah
+1 Agreed Jacques,
Same applies for images webapp located at common-themes/webapp/images.
I tried to cleanup code, as always I'll help on this :)
Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co
On Fri, Oct 27, 2017 at 1:55 PM, Jacques Le Roux <
Hi,
We have a lot of images in https://ofbiz.apache.org/images/ and its subdirectory
Viewing them, I guess some are now useless. If we keep all useless images when we will update again the site it will be a mess to recognise the images
really used and to chose among them, the fewer the better.
On Thu, Oct 26, 2017 at 7:13 AM, Taher Alkhateeb wrote:
> [...] The idea of NoSQL is to think at a different conceptual level of
> your domain model.
>
I agree! In order to leverage the power of NoSQL databases you have to
write your code accordingly and apply