Thank you Deepak for the reference link, and yes it matches with my
understanding of one and one-nofk relations. With respect to same
information, we found website is eligible candidate for maintaining the
indexes and fks for order header. So concluded to use one relation for the
field.
I think
+1 Chinmay Patidar,
As it will be good for users who want to use Bitcoins as a mode of Payments.
On Wed, Sep 27, 2017 at 6:12 PM, Chinmay Patidar <
chinmay.pati...@hotwaxsystems.com> wrote:
> Hello Devs,
>
> Ofbiz places a restriction on saving more than 3 decimal places in price
> related
Hello Devs,
Ofbiz places a restriction on saving more than 3 decimal places in price
related entity-fields. But there can be a number of use cases where a user
needs to store more than 2 or 3 decimal places in the currency related
entity-fields.
I even saw some discussions related to this but
On Wed, Sep 27, 2017 at 1:24 PM, Rishi Solanki
wrote:
> Deepak/Jacques,
>
> Thanks for the review and feedback.
>
> I propose the same in the email thread where this issue was discussed. Also
> we have consider the empty website case as well. Verified and Tested, we
>
Deepak/Jacques,
Thanks for the review and feedback.
I propose the same in the email thread where this issue was discussed. Also
we have consider the empty website case as well. Verified and Tested, we
can create order header with empty values. There are many similar relations
uses the one
Good catch Deepak!
Jacques
Le 27/09/2017 à 08:07, Deepak Dixit a écrit :
Hi Rishi/Ratnesh,
IMO relationship should be one-nofk, as website can be empty.
Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co
On Tue, Sep 26, 2017 at 8:03 PM, wrote:
Author:
Hi Rishi/Ratnesh,
IMO relationship should be one-nofk, as website can be empty.
Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co
On Tue, Sep 26, 2017 at 8:03 PM, wrote:
> Author: rishi
> Date: Tue Sep 26 14:33:05 2017
> New Revision: 1809749
>
> URL: