Re: [GENERAL] MySQL to Postgres question

2008-03-22 Thread Alvaro Herrera
Adam Rich wrote: > > The short answer is that Adam's statement is wrong, or at least > > misleading. > > Sorry Tom, I wasn't trying to do either. Joshua Drake (who I understand > to be a reliable source of postgresql information) said that applying > a sequence to a column after creation created

Re: [GENERAL] MySQL to Postgres question

2008-03-22 Thread Joshua D. Drake
On Sat, 22 Mar 2008 21:17:10 -0500 "Adam Rich" <[EMAIL PROTECTED]> wrote: > > The short answer is that Adam's statement is wrong, or at least > > misleading. > > Sorry Tom, I wasn't trying to do either. Joshua Drake (who I > understand to be a reliable source of postgresql information) said > th

Re: [GENERAL] MySQL to Postgres question

2008-03-22 Thread Adam Rich
> The short answer is that Adam's statement is wrong, or at least > misleading. Sorry Tom, I wasn't trying to do either. Joshua Drake (who I understand to be a reliable source of postgresql information) said that applying a sequence to a column after creation created issues, versus using the seri

Re: [GENERAL] MySQL to Postgres question

2008-03-22 Thread Tom Lane
"James B. Byrne" <[EMAIL PROTECTED]> writes: > On: Fri, 21 Mar 2008 13:53:36 -0500, "Adam Rich" <[EMAIL PROTECTED]> > wrote: >> I'd like to point out that using pg_dump does in fact apply sequences >> to columns after the fact. (at least in 8.3) Columns lose their >> "serial" designation after eac

Re: [GENERAL] MySQL to Postgres question

2008-03-22 Thread Joshua D. Drake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 22 Mar 2008 21:01:19 -0400 (EDT) "James B. Byrne" <[EMAIL PROTECTED]> wrote: > Message-ID: <[EMAIL PROTECTED]@sbcglobal.net> > > I am not at all > clear as to the implications of this statement but it caused me to > wonder if the primary ke

Re: [GENERAL] MySQL to Postgres question

2008-03-22 Thread James B. Byrne
Message-ID: <[EMAIL PROTECTED]@sbcglobal.net> On: Fri, 21 Mar 2008 13:53:36 -0500, "Adam Rich" <[EMAIL PROTECTED]> wrote: > > I am not sure about 8.3 but certainly earlier releases of PostgreSQL > > would have specific dependency issues when a sequence was applied to > > a column after the fact,

[GENERAL] MySQL to Postgres question

2008-03-21 Thread Edward Blake
The table I have in MySQL is similar to below: 0 SET FOREIGN_KEY_CHECKS=0; 1 CREATE TABLE products ( 2 product_id integer(11) not null auto_increment, 3 product_name varchar(255) not null, 4 product_descrition varchar(255) not null, 5 class_id integer(11) not null, 6 sub

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Paul Boddie
On 21 Mar, 17:15, [EMAIL PROTECTED] ("Edward Blake") wrote: > > When I try and rewrite it as a Postgres statement (below), it fails at line > 9. > 0 SET CONSTRAINTS ALL DEFERRED; > 1 CREATE TABLE products ( > 2 product_id serial[11] not null, > 3 product_name varchar[255] not null, >

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Adam Rich
> > I am not sure about 8.3 but certainly earlier releases of PostgreSQL > > would have specific dependency issues when a sequence was applied to > a > > a column after the fact, versus using the serial or bigserial > > psuedo-types. I'd like to point out that using pg_dump does in fact apply sequ

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Tom Lane
"Joshua D. Drake" <[EMAIL PROTECTED]> writes: >> Why > I am not sure about 8.3 but certainly earlier releases of PostgreSQL > would have specific dependency issues when a sequence was applied to a > a column after the fact, versus using the serial or bigserial > psuedo-types. As of (I think)

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Justin
Joshua D. Drake wrote: I am not sure about 8.3 but certainly earlier releases of PostgreSQL would have specific dependency issues when a sequence was applied to a a column after the fact, versus using the serial or bigserial psuedo-types. Sincerely, Joshua D. Drake - -- The PostgreSQL Comp

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Joshua D. Drake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 21 Mar 2008 12:47:38 -0500 Justin <[EMAIL PROTECTED]> wrote: > > > Why I am not sure about 8.3 but certainly earlier releases of PostgreSQL would have specific dependency issues when a sequence was applied to a a column after the fact

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Joshua D. Drake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 21 Mar 2008 12:38:49 -0500 Justin <[EMAIL PROTECTED]> wrote: > > Any ideas? > > Another way to do auto increment fields is create your own sequences. I would not suggest that. Sincerely, Joshua D. Drake - -- The PostgreSQL Company since

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Justin
Joshua D. Drake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 21 Mar 2008 12:38:49 -0500 Justin <[EMAIL PROTECTED]> wrote: Any ideas? Another way to do auto increment fields is create your own sequences. I would not suggest that. Why

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Justin
Edward Blake wrote: The table I have in MySQL is similar to below: 0 SET FOREIGN_KEY_CHECKS=0; 1 CREATE TABLE products ( 2 product_id integer(11) not null auto_increment, 3 product_name varchar(255) not null, 4 product_descrition varchar(255) not null, 5 class_id integer(

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Tom Lane
"Edward Blake" <[EMAIL PROTECTED]> writes: > When I try and rewrite it as a Postgres statement (below), it fails at line > 9. > 0 SET CONSTRAINTS ALL DEFERRED; I don't think that does the same thing as mysql's foreign_key_checks = 0. > 2 product_id serial[11] not null, This is trying to c

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Andreas 'ads' Scherbaum
Hello, On Fri, 21 Mar 2008 12:15:05 -0400 Edward Blake wrote: > 9 KEY class_id (class_id), > 10 KEY subclass_id (subclass_id), > 11 KEY department_id (department_id) this should create an index, or? You want to do this later, after table creation. Kind regards --

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Rodrigo Gonzalez
Edward Blake escribió: The table I have in MySQL is similar to below: 0 SET FOREIGN_KEY_CHECKS=0; 1 CREATE TABLE products ( 2 product_id integer(11) not null auto_increment, 3 product_name varchar(255) not null, 4 product_descrition varchar(255) not null, 5 class_id integer

Re: [GENERAL] MySQL to Postgres question

2008-03-21 Thread Joshua D. Drake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 21 Mar 2008 12:15:05 -0400 "Edward Blake" <[EMAIL PROTECTED]> wrote: > When I try and rewrite it as a Postgres statement (below), it fails > at line 9. > 0 SET CONSTRAINTS ALL DEFERRED; > 1 CREATE TABLE products ( > 2 product_id serial

[GENERAL] MySQL to Postgres question

2008-03-21 Thread Edward Blake
The table I have in MySQL is similar to below: 0 SET FOREIGN_KEY_CHECKS=0; 1 CREATE TABLE products ( 2 product_id integer(11) not null auto_increment, 3 product_name varchar(255) not null, 4 product_descrition varchar(255) not null, 5 class_id integer(11) not null, 6 sub

[GENERAL] MySQL to Postgres.

2004-06-17 Thread Prabu Subroto
Dear my friends... I am planning to migrate my database from MySQL to Postgres since the MySQL does not have subquery except it 4.1. And I can not wait until the 4.1 stable version released and included in SuSE distro. I did mysqldump (into a file, basisdata.txt) and I am going to do its query qi

[GENERAL] Mysql to postgres tools -reviews?

2001-08-30 Thread Graham White
I am looking for feedback from anyone that has moved their data from Mysql to Postgres using the tools in contrib/mysql or any other data porting tools on the net. Did any data get lost in the transfer? Recommendations? Amount of time for transfers? Any feedback would be greatly appreciated. Thank