X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3011CD1B4A2 for ; Thu, 4 Dec 2003 17:53:13 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 81688-06 for ; Thu, 4 Dec 2003 13:52:42 -0400 (AST) Received: from hotmail.com (bay9-f34.bay9.hotmail.com [64.4.47.34]) by svr1.postgresql.org (Postfix) with ESMTP id EF638D1B441 for ; Thu, 4 Dec 2003 13:52:40 -0400 (AST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 4 Dec 2003 09:52:40 -0800 Received: from 134.29.51.143 by by9fd.bay9.hotmail.msn.com with HTTP; Thu, 04 Dec 2003 17:52:40 GMT X-Originating-IP: [134.29.51.143] X-Originating-Email: [cstotes@hotmail.com] X-Sender: cstotes@hotmail.com Reply-To: cstotesbery@acm.org From: "Clint Stotesbery" To: ch@rodos.fzk.de Cc: pgsql-sql@postgresql.org Subject: Re: Help converting Oracle instead of triggers to PostgreSQL Date: Thu, 04 Dec 2003 17:52:40 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 04 Dec 2003 17:52:40.0718 (UTC) FILETIME=[695B32E0:01C3BA8F] X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/34 X-Sequence-Number: 16200 Hi Christoph, Thanks for the links but the techdoc links for converting from Oracle to PostgreSQL has 2 links that don't go to their intended targets anymore, one is in the 7.3 docs which is really limited (only covers simple things), and the Ora2Pg one I don't really get that well. As far as updateable views, that's why you need instead of triggers. Regular triggers can't be done on views. So if I make an instead of trigger on a view that's for updates then I have an updateable view. I figured it out last night and I was along the right track in my original post with using an instead of rule to call a function. The trick is that I have to pass in all the old.col and new.col stuff into the function that I call from the rule. In Oracle since the instead of stuff is a trigger I had access to the new.col and old.col stuff. To do it in PostgreSQL rules I had to pass it all in. I'm going to write a doc about the problems I've encountered during my conversion project and then submit it to the Postgres people I think (to who though?). My programming and tech writing background should help I hope. Thanks for the suggestions Christoph. -Clint ----Original Message Follows---- From: Christoph Haller To: cstotesbery@acm.org CC: pgsql-sql@postgresql.org Subject: Re: [SQL] Help converting Oracle instead of triggers to PostgreSQL Date: Thu, 04 Dec 2003 17:16:32 MET Not sure if this is of any help ... AFAIK there are no updatable views in pg. But aside from that, I cannot see nothing what could not be done by a pg trigger function: CREATE TRIGGER name { BEFORE | AFTER } { event [OR ...] } ON table FOR EACH { ROW | STATEMENT } EXECUTE PROCEDURE func ( arguments ) Also try http://techdocs.postgresql.org/#convertfrom Converting from other Databases to PostgreSQL and/or http://openacs.org/search/search?q=oracle+to+pg+porting&t=Search HTH Regards, Christoph ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html _________________________________________________________________ Get holiday tips for festive fun. http://special.msn.com/network/happyholidays.armx