>> Use Integer.
>
> It would send 4 bytes while one would do... as I sayd a lot of those
> records would be sent back and forth between client and serves and to
> optimize for speed I want to make the size of one row as small as
> possible. I know it looks like a premature optimization but my past
> expierence is that pulling data from DB is the main bottleneck in the kind
> of app I'm creating.
>
> If there is a good reason not to use CHAR(1) then at least SMALLINT would
> be better than INTEGER in case only 8 bits is required, no?
>
> BTW, I now noted that size of NUMERIC and DECIMAL is documented as
> "variable, 16, 32 or 64 bits" so perhaps NUMERIC(1) is still a good way to
> go?
>

SMALLINT?

With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!

Database questions? Check the forum:
http://www.databasedevelopmentforum.com