USING CB 1.2 RC3

When building a large community with many user-registration I encountered a mayor structural flaw in Community Builder.

Because all CB-fields are added in one Table called "comprofiler". You get a serious restriction in the total amount of fields you can add!

I've reached that total amount of data in one Table, as you can see in the code-block below!


[code:1]moscomprofilerFields::«»store failed: CBSQLupgrader::changeColumn (ADD) of Table #__comprofiler Column cb_5c3communitynaam failed with SQL error: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `jos_comprofiler`\n ADD `cb_5c3communitynaam` varchar(255) DEFAULT NULL Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `jos_comprofiler`\n ADD `cb_5c3communitynaam` varchar(255) DEFAULT NULL[/code:1]

As it says, i've reached the maximum ammount of field-data a table can contain.

In order to let Community Builder evolve, we maybe need to change this data-structure dramaticly!
Because nothing seems to be joined, this reaches serious limitations.


Yes, I've reached the limit of Community Builder.
But this doesn't have to be a limitation of CB!


Perhaps there is a sollution to this:
You can let Community Builder build a new database-table for each new Tab that is created within the CB admin.
Because all information is then devided by tabs, and so, all data-fields containing this tab are stored in different database-tables, you minimize the possibility of reaching this database-entry-limit.

Please feel free to discus this!
And hopefully the development team will have a look at this important issue.

Best regards,
stefan @ dpdk

(NED)