Question

Many times my users have complained that they get this message due to long answers. So I have to change it in core manually. But why not to increase it in core because many professional websites would be facing same problem like me.

Comments

Good suggestion. I also have the same experience. In particular, it seems to occur when we copied a complex HTML. Program changes is easy. But, to do this, database changes is also required. I worry about character size limitations and MySQL performance of innoDB.

Limit of textarea is 32,767 bytes (OK).
Limit of varchar is 65,535 bytes / 21,845 UTF-character (OK).

Reference:
http://dev.mysql.com/doc/refman/5.0/en/string-type-overview.html
http://stackoverflow.com/questions/19472004/mysql-innodb-varchar-performance-versus-text-on-inserts
http://stackoverflow.com/questions/1962310/importance-of-varchar-length-in-mysql-table
https://www.percona.com/blog/2010/02/09/blob-storage-in-innodb/

Do you have a reliable information?

---

Sorry sama but I am not the guy with much knowledge about coding. I can tell you different ways to promote your software but this coding part you have to figure out on your own. I hope you understand.

---

Do not worry. My word of "you" means everyone (e.g. Vanbells , etc). Gideon is a database specialist. So, there is surely why he was limited to 8000. I want to know it.

---

There have a been a debate about this issue on q2a http://www.question2answer.org/qa/39622/there-efficiency-security-concerns-increasing-content-limit

I believe Gideon used varchar for performance reasons.

The logical way to increase the the character length is by changing  from VARCHAR to text (longtext, medium text etc). Text takes a long time especially during an update query compared to varchar. So I believe maybe we can run some bench marks?

I still dont know why he chose 8000 though. He might have a very good reason for that or maybe it was a random figure but we can run some tests with varying figures.