Thread: 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.
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 >
> 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 > I like the idea myself of a 'library' that when placed first in the 'search path' would allow an application designed for a MSSQL database to operate. Obviously a similar library for Oracle, MySQL and others would also be benefical. They could have the affect of increasing PostgreSQL's use by reducing the immediate porting requirements. I do not know if this is possible but it would be cool stuff. Kind Regards, Keith ______________________________________________ 99main Internet Services http://www.99main.com