[Vtigercrm-developers] different modules sharing a common table?
prasad at vtiger.com
Wed Sep 21 17:28:16 GMT 2016
As long as the field is mapped with target-table or column through
follows the Entity module convention system would continue to work.
Shared table pose challenge when different module records enables edits of
It would also come in the way of performance (specifically query cache
If modules are from different publishers then sharing table is not a good
as the control or convention can be too tedious to maintain / manage.
FB <http://www.facebook.com/vtiger> I Twit <http://twitter.com/vtigercrm> I
LIn <https://www.linkedin.com/company/1270573?trk=tyah> I Blog
<https://blogs.vtiger.com> I Website <https://www.vtiger.com/>
On Wed, Sep 21, 2016 at 8:51 PM, Alan Lord <alanslists at gmail.com> wrote:
> Suppose I want to create a bunch of new modules with a set of data fields,
> but each module will also need some specific fields unique to it.
> I can think of two ways of doing this:
> Use different basetables for each module's specific data and have a common
> related table to store the common data.
> Use a common basetable and have different related tables for the specifics.
> These will all be entity records so will have unique crmids so I am
> wondering if there are any pros or cons to either approach.
> I am minded to go for the second approach personally...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtigercrm-developers