× 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.


  1.  Home
  2. MIDRANGE-L
  3. May 2005

SQL time field & CCSID?

Folks:

Anyone know why, when I create a time field in a table using SQL, it is
assigned a CCSID (37 in my case).

Logically date, time, or timestamp fields are absolute values and not
subject to character set variations.

When I execute the following SQL statement ...

ALTER TABLE DEVDMGWRK/AUTLIST ALTER COLUMN FIELD1 SET DATA TYPE TIME NOT
NULL WITH DEFAULT ccsid 37

... I get the error 'FOR DATA or CCSID clause not valid for specified
type.'.

However, when I do a DSPFFD on the file and look at the fields...

FIELD1     TIME            8       8       129        Both     FIELD1
  Time Format . . . . . . . . . . . . . . . :  *ISO
  Coded Character Set Identifier  . . . . . :     37

... I see the time field as a CCSID associated with it.

Is this just a default value that really has no relevance?

Thanks!

david

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.