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

PG, Crystal Reports, Stored Procedures and User Defined Functions

From: Philip Rhoades <pri(at)chu(dot)com(dot)au>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: PG, Crystal Reports, Stored Procedures and User Defined Functions
Date: 2002-10-30 09:20:26
Message-ID: 20021030092026.GA15166@phil.chu.com.au (view raw or flat)
Thread:
Lists: pgsql-hackers
People,

I posted this to the general list with no response so this is the next 
step . .

I have a client that I have just changed over to PG 7.2.3 and despite 
the early teething problems things are going pretty well.  There are, 
however, a few more difficult problems to do with reporting via Crystal 
Reports that could easily be solved by Stored Procedures but these 
don't exist in PG.  The User Definable Functions, which would be able 
to do the job, are not visible to CR.

There is a white paper from Crystal Decisions about how Oracle Stored 
Procedures are packaged to enable them to be used by CR.

http://support.crystaldecisions.com/library/kbase/articles/c2010910.asp

Maybe the issue really lies with psqlODBC?

Does anyone know anything about this area?  If you do, do you think it 
might be possible to also package PG functions to look like stored 
procedures to CR?  If, so is anyone interested in doing the (paid) 
work?  I am quite happy for the result to be GPLd.

Thanks,

Phil.
-- 
Philip Rhoades

Pricom Pty Limited  (ACN  003 252 275)
GPO Box 3411
Sydney NSW	2001
Australia
Mobile:  +61:0411-185-652
Fax:  +61:2:8923-5363
E-mail:  pri(at)chu(dot)com(dot)au
----- End Forwarded Message -----

-- 
Philip Rhoades

Pricom Pty Limited  (ACN  003 252 275)
GPO Box 3411
Sydney NSW	2001
Australia
Mobile:  +61:0411-185-652
Fax:  +61:2:8923-5363
E-mail:  pri(at)chu(dot)com(dot)au

Responses

pgsql-hackers by date

Next:From: Adam WitneyDate: 2002-10-30 09:25:51
Subject: Re: 7.3b3 on MacOSX 10.2.1
Previous:From: Tommi MaekitaloDate: 2002-10-30 09:03:34
Subject: tabcompletition and schema

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