Switching to varchar will probably have no negative DB side-effects (I
know it won't on Oracle). Also if you don't use the Modeler for DB
generation on this project, you can model this column as VARCHAR in the
DataMap, leaving it as CHAR in the DB.
I am not sure what would be a good general solution... I guess at some
point we should allow to explicitly turn trimming on/off at the DB
adapter level.
Andrus
On Sep 17, 2004, at 7:28 PM, Mike Kienenberger wrote:
> Tore Halset <halse..vv.ntnu.no> wrote:
>> Our database uses char(1) one some status columns. Should we switch to
>> varchar(1)? We also have som columns with char(8) that is a id that
>> always is 8 chars long. No trailing spaces. It seems a bit wasted to
>> use varchar on these fields. What do you guys think?
>
> Depends on your database and on your data size. For example, OpenBase
> makes
> no distinction between char and varchar.
>
> If your database makes a distinction, it's a space/performance
> tradeoff.
> Neither one is probably significant in this day and age.
>
> -Mike
>
This archive was generated by hypermail 2.0.0 : Sat Sep 18 2004 - 20:50:52 EDT