Thank you for your cool reply.
Best Regards
Tanakorn Numrubporn
Mridul Pathak-2 wrote:
>
> No foreign key indices are maintained for the one-nofk relationship, that
> is
> the reason why no foreign key constraints apply to a one-nofk
> relationship.
> This may be the reason that you are not a
No foreign key indices are maintained for the one-nofk relationship, that is
the reason why no foreign key constraints apply to a one-nofk relationship.
This may be the reason that you are not able to locate this relation is the
constraint part. You can find this relationship in the Webtools appl
Sorry for asking another question. When I see to the "Real Database" that
OFBiz just constructed and look in to the constraint part of
"PaymentBudgetAllocation" I can't see any thing that point to the "one-nofk"
thing. It show only which is "one" thing in database. Is that mean, It
doesn't matter
Thank you very much for your kindly reply. Your reply make my brain get fresh
(but still dumb)
Thank you again
Tanakorn Numrubporn
Rishi Solanki wrote:
>
> The relation-type = nofk is used when we need a relation but don't want to
> apply foreign key constraints on it.
> This relation comes in
The relation-type = nofk is used when we need a relation but don't want to
apply foreign key constraints on it.
This relation comes in existance only when we need to use the attribute of a
entity into another entity. And we needed
that when we delete/expire a record from entity say
"PaymentBudgetAl
I see you intent to make two of compound key (budgetId and budgetItemSeqId)
of PaymentBudgetAllocation entity have relation-type = nofk that not similar
to "The Data Model Resource Book Vol.1" in Figure 8.10. I think you have to
has a good reason for implementation
/applications/accounting/entity
