X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 99C81D1C9D8 for ; Fri, 1 Aug 2003 01:10:53 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 98994-08 for ; Thu, 31 Jul 2003 22:09:48 -0300 (ADT) Received: from calma.pair.com (calma.pair.com [209.68.1.95]) by svr1.postgresql.org (Postfix) with SMTP id CE4F3D1C977 for ; Thu, 31 Jul 2003 22:10:51 -0300 (ADT) Received: (qmail 9801 invoked by uid 3059); 1 Aug 2003 01:10:52 -0000 Date: Thu, 31 Jul 2003 21:10:52 -0400 From: "Chad N. Tindel" To: pgsql-docs@postgresql.org Subject: Mysql -> Postgresql pitfalls Message-ID: <20030801011052.GA9529@calma.pair.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/1 X-Sequence-Number: 1861 Hello- I was exchanging some email with Tom Lane about some problems I was running into converting from mysql to postgresql. He suggested I contact this list. Is there some sort of document describing common mysql->pgsql pitfalls? If not, I'd be happy to start one with the things I've run into. Who would I talk to about that? I'm not on this list, so please CC me if you reply to this message. Thanks, Chad