Change Data Type

%3CLINGO-SUB%20id%3D%22lingo-sub-2272523%22%20slang%3D%22en-US%22%3EChange%20Data%20Type%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272523%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20anyone%20see%20any%20potential%20harm%20with%20changing%20a%20field%20type%20from%20short%20text%20to%20long%20text%3F%20I%20have%20a%20inherited%20db%20that%20has%20a%20field%20designated%20as%20short%20text.%20At%20design%20time%2C%20discussion%20decided%20that%20there%20would%20never%20be%20a%20need%20for%20more%20than%20255%20chars.%20I%20guess%20the%20saying%20never%20say%20never%20is%20true.%20Now%20they%20need%20more%20characters.%20There%20is%20no%20index%20on%20the%20field.%3C%2FP%3E%3CP%3ESee%20any%20harm%20in%20changing%20the%20type%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2272523%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

Can anyone see any potential harm with changing a field type from short text to long text? I have a inherited db that has a field designated as short text. At design time, discussion decided that there would never be a need for more than 255 chars. I guess the saying never say never is true. Now they need more characters. There is no index on the field.

See any harm in changing the type?

1 Reply

@TomKosel In general, no, there should be no problems with storing additional data. 

That said, there are some differences in the way Long Text and Short Text datatypes can behave, so you do need to be aware of things that might be different. Two that come to mind are Text Format and Append Only. Both supported in Long Text. You can insert either Plain Text or Rich Text in a Long Text field (Support for fonts and colors, etc.) You can designate how new text is added. Since these are NOT properties you'd have used with Short Text, though, it should not be an issue.

longtextproperties.jpg