| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mike Mascari <mascarm(at)mascari(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Postgres Analysis Tool-Pak |
| Date: | 2000-05-20 06:30:21 |
| Message-ID: | 12056.958804221@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mike Mascari <mascarm(at)mascari(dot)com> writes:
> I've been able to implement around 300 of the 320 Excel-style
> functions and was wondering if they would be useful to
> PostgreSQL.
Seems like we could certainly stick these into a contrib directory.
I'd be a little hesitant to cram so many names into the default
installation, for fear of conflicting with existing user setups ---
but a contrib distribution has no such constraint. (Also, aren't
some of these the same as ODBC-standard functions? I believe Thomas
has been working on including all the ODBC functions into the backend,
so you could save him some work there.)
> Or I could just wait until the rewrite if the function call interface
> is going to change dramatically for this such as NULL handling etc.
What I have done so far cleans up NULL handling, but I have not tried to
do anything about functions accepting or returning sets. I think the
plan is to see if we can support set functions better as part of the
querytree redesign scheduled for 7.2.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kate | 2000-05-20 07:28:19 | contextual search |
| Previous Message | Tom Lane | 2000-05-20 05:30:08 | Re: Performance (was: The New Slashdot Setup (includes MySql server)) |