When entering a file description, it allows you to type as long as you want, however when submitting into the database it's not actually saving all data entered.
ex: I uploaded a file with the following description:
very nice looking splash page. When you mouse over apply, the button gets slightly larger in size. It gives 3 you key focal point elements, links to a free example and answers virtually all questions / concerns that a user might normally have. It also has great placement of the verisign & hacker safe logo so that users have confidence purchasing from them.
after it submitted, all that was saved and displayed is what's written below:
very nice looking splash page. When you mouse over apply, the button gets slightly larger in size. It gives 3 you key focal point elements, links to a free example and answers virtually all questions / concerns that a user might normally have. It also
Ibn Saeed
Apr 30 2007, 17:22
Hello
Yes, i think the problem is that in the table column size. Its presently set to
CODE
" VARCHAR 255"
As you can clearly see that there is a maximum character length which is 255. That is why the description was cut to 255 characters.
Under Table:
CODE
ns_fn_file
Change the field from
CODE
VARCHAR to MEDIUMTEXT
I tested it and it worked.
Sergey
Apr 30 2007, 21:49
Hello,
Actually, just type "TEXT" (not MEDIUMTEXT which is larger) will already give you 65536 available characters for the description which should be more then enough. We will change the type of this field to TEXT in 1.2.0 version.
Ibn Saeed
May 1 2007, 04:51
Hello
I thought Mediumtext would be smaller than Text.
Hello,
No you were wrong, here is the description of these field types in the MySQL docs:
http://dev.mysql.com/doc/refman/5.0/en/sto...quirements.htmlQUOTE
BLOB, TEXT -- L+2 bytes, where L < 2^16
MEDIUMBLOB, MEDIUMTEXT -- L+3 bytes, where L < 2^24
TINYTEXT is smaller then TEXT though.
I wanted to let you know that we applied those changes before posting the "bug" here, just thought you would want to address this so that it's included in future releases so others might not run into a similar problem