Suggestion for db fields length/type

[man.of.earth]

Hello,

I'd suggest that the product short description to be increased from 2000 characters (maybe text type). I have several products that exceed this 2000 characters limit (mostly because of microdata in short description), so I have to modify varchar(2000) to text each time there is a VM update.
Also, I have few products which's titles exceed 126 characters, so maybe this limit could be increased too.
Thank you.

[AH]

(mostly because of microdata in short description)

Short description - 200o characters is enough - you are clearly using this for another purpose for which it is not intended

Microdata is served using snippet sublayout

[man.of.earth]

Some of them have 700-800 characters, but I use Book type microdata, and thus they get over 2000. I made the short_desc DB field text instead of varchar(2000), and I update it every time I update VM.

[Studio 42]

@arcturus
Add a customfield type > editor to add your microdata for eg. and modify the render so no label and other HTML is added is the right way to do it.
If it not work because text field length, you can make a plugin and use parameters and you can do your own form to easy insert your microdatas.
Parameters can use 65500 chars.

[AH]

I'd suggest that the product short description to be increased from 2000 characters (maybe text type). I have several products that exceed this 2000 characters limit (mostly because of microdata in short description), so I have to modify varchar(2000) to text each time there is a VM update.
Also, I have few products which's titles exceed 126 characters, so maybe this limit could be increased too.

Just requesting a change in length of a core field(s) told the forum nothing of use.

With a better understanding of your business requirement - it is easier to see what you are trying to achieve and that you are (as noted) using the short description to meet your own needs when another base piece of functionality is already provided to support unique/specific business requirements.

See the good solution response from Studio42

Neither of your requests should make any core release

[Studio 42]

H1 should not exced 80 chars.
More then 120 chars can be simply bad for SEO, a user never search for a so long sentence and you dilute the power of the H1.