Dennis Heuer wrote:
> your column types are somewhat unclean. For example, why you use INT
> for a boolean value. The most close type would be TINYINT (SMALLINT
> where TINYINT isn't supported). Using a CHAR(1) and character-set
> safe binar values like \x60 and \x61 is another alternative.
>
> Your StringCol(length) seems to be byte-oriented. It would be nice if
> there was a character-based length attribute.
A lot of these issues are database-specific. E.g., character vs. byte
lengths; I don't know how that would work in all the different
databases. BOOLEAN is another database-specific thing -- I think
TINYINT is used for some backends, BOOLEAN elsewhere, maybe INT for a
couple places. Often it doesn't really matter, as some of these data
types are holdovers from times when resources were more restricted.
--
Ian Bicking / ia...@co... / http://blog.ianbicking.org
|
