In one of my objects I have lots of text stores in text area fields, and often get the following error message when I try to save a record:
Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline
I'm just not sure where I can access these settings. Is it possible to store more text in records?
Thank you,
Greg
In one of my objects I have lots of text stores in text area fields, and often get the following error message when I try to save a record:
Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline
I'm just not sure where I can access these settings. Is it possible to store more text in records?
Thank you,
Greg
Flag this post as spam/abuse.
Thank you very much, Pradeep. I am on public cloud -- is there anything I can do?
Greg
We are looking into fixing this in Public Cloud. Can you describe the scenario of getting this error.
I am adding content to text area fields from the opportunity edit view. When I click on save, the error message above comes up, and none of the new text I just entered is saved. Is there any other information you need? Thank you!
Greg
Thank for the test case. We will be fixing this in an upcoming update to rollbase.com
Thank you very much!!
Any word on fixing this issue? It is becoming a big obstacle for my company's applications. Since it's a matter of database settings, not overall storage limits, it would be great if a public cloud account could have more control to avoid this issue. I have to split what should be one record in a single object into several records in multiple objects with one-to-one relationships. But then object views, etc. become impossible since the data is held across multiple objects.
Thank you,
Greg
Greg, apologise for the issue. Engineering has reproduced the issue. We are evaluating a fix with the database packet size and bin log size. I'll update you next week on the fix schedule.
Hello Murali,
Thank you for looking into this. Do you have any update on the timeline for fixing the issue?
Thanks,
Greg