Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.postgresql > #451

Re: migration mysql to pgsql?

Path csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From Harry Tuttle <SOZRBLNTLEEE@spammotel.com>
Newsgroups comp.databases.postgresql
Subject Re: migration mysql to pgsql?
Date Wed, 05 Jun 2013 10:09:36 +0200
Lines 30
Message-ID <b189veFigudU1@mid.individual.net> (permalink)
References <kommrr$1k2$1@news.albasani.net>
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 7bit
X-Trace individual.net qPcNSoGPz7N+1fSnSt8vuwiS1iGeH4BiFUIYt3DvqhHt9/aos=
Cancel-Lock sha1:NdKMRqNiO3jpgZF2WHbjF7eHOxc=
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
In-Reply-To <kommrr$1k2$1@news.albasani.net>
Xref csiph.com comp.databases.postgresql:451

Show key headers only | View raw

Magnus Warker, 05.06.2013 08:46:
> First of all I wanted to adapt the usage of table names, because I
> already know some names used in the mysql database that would case
> problems in pgsql. My idea is to use quotation marks for table names.
> Then, I could achieve two goals at once: a) avoid conflicts with key
> words, and b) preserve upper and lower case letters, which I use in
> mysql and which is not supported in pgsql without quotation marks.
> Would you agree that this would be a reasonable first step?
>
> However, the adaptation of the mysql db to use qoted table names
> already is a problem, because mysql does not seem to like it. Does
> someone have an idea how to deal with this?

MySQL does support standard ANSI quoting (using " instead of the dreaded `) if configured correctly.

Another good approach would be to change MySQL to be more ANSI compliant by using the following sql_mode options:

   ANSI
   NO_BACKSLASH_ESCAPES
   STRICT_ALL_TABLES
   NO_AUTO_VALUE_ON_ZERO
   NO_ZERO_DATE
   NO_ZERO_IN_DATE
   PIPES_AS_CONCAT
   ONLY_FULL_GROUP_BY
   ERROR_FOR_DIVISION_BY_ZERO

But I would take the opportunity and get rid of quoted identifiers alltogether if you are at it.
In my experience they don't really add any advantages but generate problems in various tools.

Back to comp.databases.postgresql | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

migration mysql to pgsql? Magnus Warker <warker@mailinator.com> - 2013-06-05 08:46 +0200
  Re: migration mysql to pgsql? Harry Tuttle <SOZRBLNTLEEE@spammotel.com> - 2013-06-05 10:09 +0200
    Re: migration mysql to pgsql? Magnus Warker <warker@mailinator.com> - 2013-06-05 11:43 +0200
      Re: migration mysql to pgsql? Harry Tuttle <SOZRBLNTLEEE@spammotel.com> - 2013-06-05 11:59 +0200
        Re: migration mysql to pgsql? Magnus Warker <warker@mailinator.com> - 2013-06-05 13:06 +0200
          Re: migration mysql to pgsql? Robert Klemme <shortcutter@googlemail.com> - 2013-06-05 21:30 +0200
      Re: migration mysql to pgsql? Stefan+Usenet@Froehlich.Priv.at (Stefan Froehlich) - 2013-06-05 10:59 +0000
  Re: migration mysql to pgsql? Walter Hurry <walterhurry@lavabit.com> - 2013-06-07 21:52 +0000
    Re: migration mysql to pgsql? gargoyle60 <gargoyle60@example.invalid> - 2013-06-08 09:12 +0100
  Re: migration mysql to pgsql? johannes falcone <visphatesjava@gmail.com> - 2013-06-18 12:03 -0700

csiph-web