| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Moray McConnachie <moray(dot)mcconnachie(at)computing-services(dot)oxford(dot)ac(dot)uk>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Re: missing function datetime() |
| Date: | 2000-02-28 16:26:42 |
| Message-ID: | 38BAA1C2.65971352@alumni.caltech.edu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
> I can see two ways to do that: either add another function to pg_proc
> (five of them actually :-(), or hack the parser to translate a function
> name 'datetime' to 'timestamp'. Ugly as the second one sounds, it has
> a couple of advantages. First, it would provide an automatic upgrade
> path: future dumps of 7.0 databases would show the correct function
> name, at least for uses in rules. So we could hope to get rid of the
> compatibility hack someday. Second, the parser has special treatment
> for functions that are named the same as datatypes --- it knows they
> represent type coercions --- so a function named "datetime" won't really
> work quite the way it should for type resolution.
xlateSqlFunc() is already in gram.y; enjoy...
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-02-28 16:36:26 | Re: [HACKERS] interesting observatation regarding views and V7.0 |
| Previous Message | Tom Lane | 2000-02-28 16:26:35 | Re: [HACKERS] Re: missing function datetime() |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abdul Karim | 2000-02-28 16:42:42 | importing data from a text file |
| Previous Message | Tom Lane | 2000-02-28 16:26:35 | Re: [HACKERS] Re: missing function datetime() |