Subject | Re: [Firebird-Architect] Record Encoding |
---|---|
Author | Steen Jansdal |
Post date | 2005-05-13T07:24:57Z |
Jim Starkey wrote:
The same goes for integers. Why define if an integer should
be SMALLINT, INTEGER or BIGINT?
Steen
><..snip..>
><..snip..>
> The density is nice, but the thing that excites me most about the
> encoding as an ODS structure is that it utterly eliminates any
> dependency on physical field length. I'm toying with the idea of
> replacing "varchar (<size>)" with a just "string" in Netfrastructure.
> Fixed field lengths made perfectly good sense for punch cards, but I
> think we're past that now.
>
The same goes for integers. Why define if an integer should
be SMALLINT, INTEGER or BIGINT?
Steen