On Mon, Apr 27, 2009 at 03:13:09PM +0200, Matej Hasul wrote:
Hello, I started working on migrating tables to mysql.
Data types conversion looks like this:
varchar2 - varchar
number - numeric
date - timestamp
Following problems emerged:
1. Mysql doesn`t support user defined data type.
On Tue, Apr 28, 2009 at 10:10:01AM -0400, Tom Lane wrote:
The usual experience AFAIR is that the queries have to be dumbed down to
the point that they no longer perform well on Oracle (or Postgres),
because of mysql's crummy optimizer and lack of support for advanced
join strategies.
A lot
Hello, I started working on migrating tables to mysql.
Data types conversion looks like this:
varchar2 - varchar
number - numeric
date - timestamp
Following problems emerged:
1. Mysql doesn`t support user defined data type. So I have no idea what to
do with evr_t.
2. Mysql doesn`t support
Matej Hasul wrote:
Hello, I started working on migrating tables to mysql.
Data types conversion looks like this:
varchar2 - varchar
number - numeric
date - timestamp
For the records. Matej is trying to rewrite queries in run time to be
MySQL compatible...
Following problems emerged:
1.
Matej Hasul matej.ha...@gmail.com writes:
Hello, I started working on migrating tables to mysql.
Isn't this a complete waste of time? There is exactly 0 chance of
migrating all those procedures to mysql.
regards, tom lane
___
Tom Lane wrote:
Matej Hasul matej.ha...@gmail.com writes:
Hello, I started working on migrating tables to mysql.
Isn't this a complete waste of time? There is exactly 0 chance of
migrating all those procedures to mysql.
How do you know?
--
Miroslav Suchy
Red Hat Satellite Engineering
=?ISO-8859-2?Q?Miroslav_Such=FD?= msu...@redhat.com writes:
Tom Lane wrote:
Isn't this a complete waste of time? There is exactly 0 chance of
migrating all those procedures to mysql.
How do you know?
Try it for awhile and see what you think. The incompatibilities and
missing features
