Re: One byte integer

you can do CHAR(1) for BIT data

which prevents automatic conversion, the DB treats it as binary data.

Charles


On Mon, Mar 25, 2013 at 10:32 AM, Raul A. Jager W. <raul@xxxxxxxxxx> wrote:

SMALL INT uses two bytes, and allows values between -32.000 something to
+ 32.000
I need a field for values between 0 and 100, if possible using one byte.
One way to do it is to define as 1 BYTE binnary and overlap in a DS, but
if it is the only way I will use two bytes.

Michael Schutte wrote:

Wouldn't that be SMALLINT

You have SMALLINT, INTEGER and BIGINT in SQL. I don't know about
unsigned.

On Mon, Mar 25, 2013 at 10:12 AM, Raul A. Jager W. <raul@xxxxxxxxxx>

wrote:

In RPG (and other languages) I can declare a 1 Byte number, signde for
-128 to 127 and unsigned 0 to 255, wich will be something like a "half
small integer".

But I clould not find a way to define such a field in SQL. Is it

possible?

TIA
Raul


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.