I was looking over the "FIXME" marks within the information_schema.sql, and the last ones left (after my previous patch) are for interval_type and interval_precision. It looks to me as if the standard is differentiating between datetime_precision and interval_precision (see attached patch), so I pulled those apart (for one view). Does anyone know what is supposed to go into the interval_type field?
Thanks, -- Greg Sabino Mullane [EMAIL PROTECTED] End Point Corporation PGP Key: 0x14964AC8 200608241454 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
Index: information_schema.sql
===================================================================
RCS file: /projects/cvsroot/pgsql/src/backend/catalog/information_schema.sql,v
retrieving revision 1.33
diff -u -c -r1.33 information_schema.sql
*** information_schema.sql 2 Apr 2006 17:38:13 -0000 1.33
--- information_schema.sql 24 Aug 2006 18:49:48 -0000
***************
*** 306,313 ****
AS cardinal_number)
AS datetime_precision,
CAST(null AS character_data) AS interval_type, -- FIXME
! CAST(null AS character_data) AS interval_precision, -- FIXME
CAST(current_database() AS sql_identifier) AS attribute_udt_catalog,
CAST(nt.nspname AS sql_identifier) AS attribute_udt_schema,
--- 306,324 ----
AS cardinal_number)
AS datetime_precision,
+ CAST(
+ CASE WHEN a.atttypid = 1186 THEN NULL ELSE
+ _pg_datetime_precision(_pg_truetypid(a, t), _pg_truetypmod(a, t))
+ END AS cardinal_number)
+ AS datetime_precision,
+
CAST(null AS character_data) AS interval_type, -- FIXME
!
! CAST(
! CASE WHEN a.atttypid <> 1186 THEN NULL ELSE
! _pg_datetime_precision(_pg_truetypid(a, t), _pg_truetypmod(a, t))
! END AS cardinal_number)
! AS interval_precision,
CAST(current_database() AS sql_identifier) AS attribute_udt_catalog,
CAST(nt.nspname AS sql_identifier) AS attribute_udt_schema,
signature.asc
Description: This is a digitally signed message part
