Problem :
I have members of clubs.
CB does the job for users.
But I'd like each club to have its own fields (and tabs).
In that respect, from a development point of view, clubs become just a category of users.

This can be implemented as is in regular use of CB.

But, because the size of a record is limited in MySQL,
and for clarity sake (especially for further developments)
I would like to know whether :
- there is already a regular way to add a table,
- or, if changing the table field of a record in #__comprofiler_fields, to another table would help to keep #__comprofiler for users, but have also a #__clubs table just for clubs ?
As the fields of both are mainly different in nature, I'd like to keep these tables separated.

Thank you for your replay.
Indeed. I see that there is massive use of #__comprofiler hardcoded in CB

In that respect, the two values of the field #__comprofiler_fields.table are, and can only be #__users or #__comprofiler.

Therefore, the MVC model is not exactly working here.
May be a thought for the future : the SQL commands in CB could rely on the value in #__comprofiler_fields.table, and if different of #__comprofiler generate a JOIN.

--

For the present, I just wanted an identity form for the clubs with search possibilities and locations.
GJ has many features I do not need. But I will see how I can manage with it to just have a short presentation, with location and search.