cancel
Showing results for 
Search instead for 
Did you mean: 

deciding on the varchar strategy

tombaeyens
Champ in-the-making
Champ in-the-making
some text columns have varchar(255), some just varchar.

i think the motivation to have (255) is that some dbs handle fixed length strings much more efficient then open ended varchars.  maybe it's less portable.

we should list all arguments, decide and document the strategy.

who's got thoughts on this?
1 REPLY 1

dsyer
Champ in-the-making
Champ in-the-making
I think the default for many (most?) platforms is VARCHAR(1) which probably isn't what we want. Also not all platforms always have the "VARCHAR" alias, but that's another story (we need platform specific scripts). So we should choose an appropriate value for all the columns, and expect that users may want to tweak them in production.
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.