I have a question regarding Data Stores and entities.Let us assume I have a few

chetany

A Score Level 1

over 10 years ago

I have a question regarding Data Stores and entities.Let us assume I have a few CDTs which are being used by my app.One is a main CDT, few other CDTs are its members. (single level nesting).
While creating a Data Store, I have two options:
1. Add all entities i.e. CDTs used by my app to a single Data Store
2. Create a separate Data Store for each entity i.e. each Data Store will have a single entity.

Either way works, but I wish to know which is the best one. Are there any use-cases where one option can be preferred over other?

Discussion posts and replies are publicly visible

0 PhilB
A Score Level 1
over 10 years ago

If the CDTs are nested then they must be entities in the same data store as the parent, which may limit you to a single data store in a number of cases. It's often worth using multiple data stores when you have multiple applications for which you want be able to publish / deploy data entities separately; a single data store per CDT would seem excessive but that's not to say that it hasn't been done.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 chetany
A Score Level 1
over 10 years ago

Thank you Phil for sharing your view. I am now inclined to using one data store for all entities since the CDTs are nested.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rajatm over 10 years ago

Also, if you do not want to query the nested tables separately then it is fine. But if you do have a need to query those then you will have to keep those separate and not nested.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 PhilB
A Score Level 1
over 10 years ago

That's not the case; it's absolutely fine to build query rules against the nested elements of the CDT just as you would with any other CDT.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel