Re: Conversion ideas (Views/procedures) - Mailing list pgsql-sql

From KÖPFERL Robert
Subject Re: Conversion ideas (Views/procedures)
Date
Msg-id ED4E30DD9C43D5118DFB00508BBBA76EB16574@neptun.sonorys.at
Whole thread Raw
In response to Conversion ideas (Views/procedures)  ("Joel Fradkin" <jfradkin@wazagua.com>)
List pgsql-sql
As so often, I would suggest regular languages to accomplish most of the
work that comes up.
Use for example ours all friend 'sed' to edit a big sql-dump.

you can for example simply replace isnull(X) by X is null.
RegEx will possibly not reach for all posibilities but the're very good for
the first big steps towards your goal.


> -----Original Message-----
> From: Joel Fradkin [mailto:jfradkin@wazagua.com]
> Sent: Mittwoch, 19. Jänner 2005 16:23
> To: pgsql-sql@postgresql.org
> Subject: [SQL] Conversion ideas (Views/procedures)
>
>
> I am new to Postgres and am converting our MSSQL database to Postgres.
>
> I just did my first function.
> My question is does it make sense to create functions for
> some of the common
> functionality available to the MSSQL world (left, isnull,
> etc) so I do not
> need visit every view, and stored procedure to remove them?
> If it does is there a body of work anywhere?
> If not what is the best approach just remove all non existent
> (re-engineer)
> functions from my views and procedures. I understand some of
> the items are
> available, but a bit different either the name of the
> function or its use. I
> did see a how to that alerted me to the datefiff being
> date_diff and to
> watch out for the yy needing to be 'year' etc. he mentioned to use
> coalesce() instead of isnull also. Any other common ones I
> should be aware
> of?
>
>
> Joel Fradkin
>  
> Wazagua, LLC
> 2520 Trailmate Dr
> Sarasota, Florida 34243
> Tel.  941-753-7111 ext 305
>  
> jfradkin@wazagua.com
> www.wazagua.com
> Powered by Wazagua
> Providing you with the latest Web-based technology & advanced tools.
> © 2004. WAZAGUA, LLC. All rights reserved. WAZAGUA, LLC
>  This email message is for the use of the intended
> recipient(s) and may
> contain confidential and privileged information.  Any
> unauthorized review,
> use, disclosure or distribution is prohibited.  If you are
> not the intended
> recipient, please contact the sender by reply email and
> delete and destroy
> all copies of the original message, including attachments.
>  
>
>  
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>


pgsql-sql by date:

Previous
From: "Joel Fradkin"
Date:
Subject: Conversion ideas (Views/procedures)
Next
From: Michael Fuhr
Date:
Subject: Re: Returning a bool on DELETE in a proc.