Archives of the TeradataForum

Message Posted: Wed, 17 Jul 2002 @ 13:34:44 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I have a table (see below)

CREATE SET TABLE PGS ,NO FALLBACK ,
     NO BEFORE JOURNAL,
     NO AFTER JOURNAL
     (
      StoreNumber INTEGER TITLE 'Store Number' NOT NULL,
      CommodityCode CHAR(3) CHARACTER SET LATIN NOT CASESPECIFIC TITLE 'Prism Commodity Code' NOT NULL,
      MonthID INTEGER TITLE 'Month ID' NOT NULL,
      Gallons DECIMAL(10,0) TITLE 'Gallons',
     )
UNIQUE PRIMARY INDEX  ( StoreNumber ,CommodityCode ,MonthID );

which when selecting rows from this table returns a '***' for the Gallons (for every single row).

Yet in another table (see below) with decimal values with a much bigger definition, it displays the values correctly (Units and RetailAmount come out as specified with 3 and 2 digits after the decimal point respectively).

CREATE SET TABLE SST ,NO FALLBACK ,
     NO BEFORE JOURNAL,
     NO AFTER JOURNAL
     (
      MonthID INTEGER NOT NULL,
      StoreNumber INTEGER NOT NULL,
      InventoryType CHAR(1) CHARACTER SET LATIN NOT CASESPECIFIC,
      Units DECIMAL(14,3),
      RetailAmount DECIMAL(17,2)
     )
PRIMARY INDEX  ( MonthID ,StoreNumber )
INDEX MonthID_IDX_MTH ( MonthID ) ORDER BY VALUES ( MonthID )
INDEX StoreNumber_IDX_MTH ( StoreNumber );

I have ODBC version 3.00.00.00 and Queryman version 5.2.0.

Does anyone know what is causing this? If so, is there a solution? (I thought about casting but it seems silly since it should be able to handle the 10,0 decimal format if it handles 14,3 and 17,2 decimal formats)

Any feedback would be helpful

Thanks,

Dara

	<Prev	Next>		<<First	<Prev	Next>	Last>>