Row size too large

14 years 5 months ago #113289 by piersol
Row size too large was created by piersol
I thought this issue was no longer an issue anymore.

i cant add any new fields or plugins with fields.

I use j1.5.14 cb 1.2.1 and php 5+

[code:1]moscomprofilerFields::«»store failed: CBSQLupgrader::changeColumn (ADD) of Table #__comprofiler Column cb_dfgdfg 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_dfgdfg` 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_dfgdfg` varchar(255) DEFAULT NULL[/code:1]

Please Log in to join the conversation.

14 years 4 months ago #116618 by romannumeralus
Replied by romannumeralus on topic Re:Row size too large
I had the same problem. I was told I had too many text fields stored as 'varchar' and needed to change some of them to other types. When I erased all the fields that weren't published I was able to add more fields. I have still run out of space and even optimized my table in the db, but there's got to be another solution.

Please Log in to join the conversation.

14 years 4 months ago #116675 by krileon
Replied by krileon on topic Re:Row size too large
romannumeralus wrote:

I had the same problem. I was told I had too many text fields stored as 'varchar' and needed to change some of them to other types. When I erased all the fields that weren't published I was able to add more fields. I have still run out of space and even optimized my table in the db, but there's got to be another solution.


Limitation of your database and/or host. There's no work around for it. Discuss this with your host or remove the excess fields.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.

Please Log in to join the conversation.

14 years 4 months ago #116683 by piersol
Replied by piersol on topic Re:Row size too large
What would the HOST have to do with the way CB was written? Beat even wrote in another post that this was related to the choice they made in writing the code as they made it a varChar which has a limit of 256. It gets above my head, but again no relation to HOST.

We already new to delete other fields. I do not believe it unwarranted to see a better solution than that.

Thanks for your response, but you did not contribute anything to advance the issue.

Please Log in to join the conversation.

14 years 4 months ago #116693 by nant
Replied by nant on topic Re:Row size too large
piersol wrote:

What would the HOST have to do with the way CB was written? Beat even wrote in another post that this was related to the choice they made in writing the code as they made it a varChar which has a limit of 256. It gets above my head, but again no relation to HOST.

We already new to delete other fields. I do not believe it unwarranted to see a better solution than that.

Thanks for your response, but you did not contribute anything to advance the issue.


Agree, its more of a MySQL limitation.

Please Log in to join the conversation.

14 years 4 months ago #116768 by romannumeralus
Replied by romannumeralus on topic Re:Row size too large
So what do I do? My client is getting very impatient and I can't blame him. Beat's solution was supposed to give me 30,000 fields. That's about 28,000 more than what I'm currently using in the db. When I changed the varchars to text, I got about 20 more. What is the problem. This is not simply a MySQL issue. It's the way CB was written to store every field in the same table. Is there a way to split the table or create fields for tabs or anything else? Is there a way to call 2 different dbs? Is there a way to make this work? Please help and address this immediately. I paid for your components and several others and it will be to no avail if I can't even add the proper fields for the profiles.

Please Log in to join the conversation.

Moderators: beatnantkrileon
Time to create page: 0.228 seconds

Facebook Twitter LinkedIn