Truncated Messgaes on Punaweb?

[Guest]

In a data base you have to dictate when you design the schema how you want the fields to work to accommodate the size and type of date to be stored.
There is
TINYINT
A very small integer
The signed range is –128 to 127. The unsigned range is 0 to 255.

SMALLINT
A small integer
The signed range is –32768 to 32767. The unsigned range is 0 to 65535

MEDIUMINT
A medium-size integer
The signed range is –8388608 to 8388607. The unsigned range is 0 to 16777215

INT or INTEGER
A normal-size integer
The signed range is –2147483648 to 2147483647. The unsigned range is 0 to 4294967295
CHAR
A fixed-length string that is always right-padded with spaces to the specified length when stored
The range of Length is 1 to 255 characters. Trailing spaces are removed when the value is retrieved. CHAR values are sorted and compared in case-insensitive fashion according to the default character set unless the BINARY keyword is given

VARCHAR
A variable-length string. Note: Trailing spaces are removed when the value is stored (this differs from the ANSI SQL specification)
The range of Length is 1 to 255 characters. VARCHAR values are sorted and compared in case-insensitive fashion unless the BINARY keyword is given

TINYBLOB,
TINYTEXT

A BLOB or TEXT column with a maximum length of 255 (2^8 - 1) characters

BLOB,
TEXT

A BLOB or TEXT column with a maximum length of 65535 (2^16 - 1) characters

MEDIUMBLOB,
MEDIUMTEXT

A BLOB or TEXT column with a maximum length of 16777215 (2^24 - 1) characters

LONGBLOB,
LONGTEXT

A BLOB or TEXT column with a maximum length of 4294967295 (2^32 - 1) characters

If the post has more data than the field can except it will truncate it.