On 25 March 2018 at 01:58, Rishi Solanki <[email protected]> wrote:
> Register new group in entityengine.xml with new name and data resource; > > <group-map group-name="your.group.name" > datasource-name="yourDataResourceName"/> > > Add new data resource entry in the entityengine.xml like we have many. In > your case entityengine will contains two entry as localmysql and > localmysql2 (or any name you prefer). > Now register all the entities with "your.group.name" in entity-group.xml. > > Refer <group-map group-name="org.apache.ofbiz.tenant" > datasource-name="localderbytenant"/> and related entries for more details. > Thanks Rishi. If you do define a new group, does that mean: - any transaction that modifies entities in two different groups will be slower as the transaction must be a distributed transaction with two-phase commit? To put it another way, with good design decisions, entity groups may well give you faster reads, but writes very likely won't be? - Foreign key constraints and thus guaranteed referential integrity might not be possible between groups because not all DBMSes support FKs that refer to another database? Thanks Paul Foxworthy -- Coherent Software Australia Pty Ltd PO Box 2773 Cheltenham Vic 3192 Australia Phone: +61 3 9585 6788 Web: http://www.coherentsoftware.com.au/ Email: [email protected]
