Skip site navigation (1) Skip section navigation (2)

Re: information_schema.columns changes needed for OLEDB

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Konstantin Izmailov <pgfizm(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: information_schema.columns changes needed for OLEDB
Date: 2009-05-29 18:35:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Konstantin Izmailov <pgfizm(at)gmail(dot)com> writes:
> you know that some Postgres functions are listed in pg_proc while others are
> not. For example, all Data Type Formatting function are in pg_proc (to_char,
> to_hex, ...). While several of the Date/Time Functions are not there
> (extract, localtime, ...).

The ones that appear not to be there are ones that the SQL standard
demands special weird syntax for.  The grammar translates such calls
to standard function calls to underlying functions, which usually are
named a bit differently to avoid confusion.  For instance
extract(field from some_expr) becomes date_part('field', some_expr).

If you want to know what all of these are, see the func_expr production
in parser/gram.y.

> This causes issues to Windows integration as well.

Complain to the SQL standards committee, especially to those members
who seem to think COBOL represented the apex of programming language
syntax design :-(

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Josh BerkusDate: 2009-05-29 18:36:45
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Previous:From: Simon RiggsDate: 2009-05-29 18:23:29
Subject: Re: Clean shutdown and warm standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group