Re: MySQL to Postgres

2007-02-06 Thread Jim C.
ViSolve DB Team wrote: > Hi, > >> From MySQL 4.1, there is a support for mysqldump --compatible option. > There is a safe/cool dump for your table: > Try lik: > shell > mysqldump -u dev -p visolvetestdb credits > --compatible=postgresql > /home/test/ps.sql > > And also, > By default tables are d

Re: MySQL to Postgres

2007-02-05 Thread Chris
Jim C. wrote: OK, I've another question. This one is about the INSERT command. When I uncomment some of these statements I get an error in regards to a comma. What I'm afraid of is that perhaps there is a compatibility issue such that an INSERT command on Postgres can't take as many records as

Re: MySQL to Postgres

2007-02-05 Thread Jochem van Dieten
On 2/5/07, Jim C. wrote: When I uncomment some of these statements I get an error in regards to a comma. What I'm afraid of is that perhaps there is a compatibility issue such that an INSERT command on Postgres can't take as many records as MySQL. What version are you running? Jochem -- MyS

Re: MySQL to Postgres

2007-02-05 Thread Jochem van Dieten
On 2/5/07, Jim C. wrote: CREATE TABLE "credits" ( "person" integer NOT NULL default '0', "chanid" int NOT NULL default '0', "starttime" timestamp NOT NULL default '1970-01-01 00:00:00+00', "role" VARCHAR NOT NULL, CONSTRAINT role_check CHECK "role" IN ('actor','director','producer','ex

Re: MySQL to Postgres

2007-02-05 Thread Jim C.
Chris White wrote: > Jim C. wrote: >>> CREATE TABLE "credits" ( >>> "person" integer NOT NULL default '0', >>> "chanid" int NOT NULL default '0', >>> "starttime" timestamp NOT NULL default '1970-01-01 00:00:00+00', >>> "role" VARCHAR NOT NULL, >>> CONSTRAINT role_check CHECK "role" IN >>

Re: MySQL to Postgres

2007-02-05 Thread Chris White
Jim C. wrote: CREATE TABLE "credits" ( "person" integer NOT NULL default '0', "chanid" int NOT NULL default '0', "starttime" timestamp NOT NULL default '1970-01-01 00:00:00+00', "role" VARCHAR NOT NULL, CONSTRAINT role_check CHECK "role" IN ('actor','director','producer','executive_pro

Re: MySQL to Postgres

2007-02-05 Thread Jim C.
OK, I've another question. This one is about the INSERT command. When I uncomment some of these statements I get an error in regards to a comma. What I'm afraid of is that perhaps there is a compatibility issue such that an INSERT command on Postgres can't take as many records as MySQL. Seems to

Re: MySQL to Postgres

2007-02-05 Thread Jim C.
> CREATE TABLE "credits" ( > "person" integer NOT NULL default '0', > "chanid" int NOT NULL default '0', > "starttime" timestamp NOT NULL default '1970-01-01 00:00:00+00', > "role" VARCHAR NOT NULL, > CONSTRAINT role_check CHECK "role" IN > ('actor','director','producer','executive_produ

Re: MySQL to Postgres

2007-02-05 Thread Jim C.
> It looks more like the person that designed the schema has payed very > little attention to the SQL standard. You can not blame anyone but the > designer for naming a field 'role' (which is a keyword in the SQL > standard) or using a non-standard set field type instead of a proper > lookup table.

Re: MySQL to Postgres

2007-02-05 Thread Jim C.
> It looks more like the person that designed the schema has payed very > little attention to the SQL standard. You can not blame anyone but the > designer for naming a field 'role' (which is a keyword in the SQL > standard) or using a non-standard set field type instead of a proper > lookup table.

Re: MySQL to Postgres

2007-02-03 Thread Jochem van Dieten
On 2/2/07, Jim C. <[EMAIL PROTECTED]> wrote: I'm having to move some data from MySQL to Postgres. I used mysqldump --compatible=postgresql, but the compatibility is extremely lacking. It looks more like the person that designed the schema has payed very little attention to the SQL standard. You

Re: MySQL to Postgres

2007-02-02 Thread ViSolve DB Team
Hi, From MySQL 4.1, there is a support for mysqldump --compatible option. There is a safe/cool dump for your table: Try lik: shell > mysqldump -u dev -p visolvetestdb credits --compatible=postgresql > /home/test/ps.sql And also, By default tables are dumped in a format optimized for MySQL.