×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I don't believe TINYINT is part of any of the SQL ANSI standards, so IBM will not likely add it.
IBM are staunch supporters of the ANSI standard and therefore you won't get all the bells and whistles that you find in other database platforms that tend to deviate from the ANSI standard.
-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Monday, March 25, 2013 11:23 AM
To: Midrange Systems Technical Discussion
Subject: Re: One byte integer
You know, you could submit a Design Change Request to add TINYINT.
https://www-912.ibm.com/r_dir/ReqDesChange.nsf/Request_for_Design_Change?OpenForm
http://community.common.org/HOME/IBMIREQ.wgs
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Raul A. Jager W." <raul@xxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 03/25/2013 11:49 AM
Subject: Re: One byte integer
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Yes, my memmory had some reference to TINYINT, but I could not find it
in DB2/400.
Now I know I must stop locking for it, and use other option.
Thanks, now I can continue to avance my project.
Raúl
Scott Klement wrote:
In some flavors of SQL there's a data type of TINYINT, which seems to be
what Raul is looking for.
Unfortunately, this doesn't exist in DB2 for i.
On 3/25/2013 9:24 AM, Luis Rodriguez wrote:
IIRC, the smallest integer field you can specify in SQL is SMALLINT,
which
is defined as (again, IIRC) as a two(2) bytes field.
midrange.com
