Received: from wallace.ece.rice.edu (wallace.ece.rice.edu [128.42.12.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e78Hu8G67572 for ; Tue, 8 Aug 2000 13:56:08 -0400 (EDT) Received: by rice.edu via sendmail from stdin id (Debian Smail3.2.0.102) for pgsql-interfaces@postgresql.org; Tue, 8 Aug 2000 12:56:03 -0500 (CDT) Date: Tue, 8 Aug 2000 12:56:03 -0500 From: "Ross J. Reedstrom" To: pgsql-interfaces@postgresql.org Subject: Re: Migration Message-ID: <20000808125603.A4598@rice.edu> Mail-Followup-To: pgsql-interfaces@postgresql.org References: <20000808095932.B3338@rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: ; from christian@oven.com on Tue, Aug 08, 2000 at 04:22:00PM +0100 X-Archive-Number: 200008/64 On Tue, Aug 08, 2000 at 04:22:00PM +0100, Christian Herbert wrote: > We are not looking to migrate to Oracle immediately... but the request is to > keep the option open for future migration. Fair enough. That's how I convinced my team to using postgresql for our project: use postgresql for development, and move to Oracle if needed for scale up. In that light, the trick is to stick with bog standard SQL: use no special features of pgsql. Or if you do, make sure they're either Oracle compatability features, or that there is a simple Oracle replacement. Ross -- Ross J. Reedstrom, Ph.D., NSBRI Research Scientist/Programmer Computer and Information Technology Institute Rice University, 6100 S. Main St., Houston, TX 77005