Re: Moving from MySQL to PGSQL....some questions (multilevel

From: Harald Fuchs <hf118(at)protecting(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Moving from MySQL to PGSQL....some questions (multilevel
Date: 2004-03-03 16:59:02
Message-ID: pu65dluasp.fsf@srv.protecting.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In article <Pine(dot)LNX(dot)4(dot)33(dot)0403021406090(dot)4475-100000(at)css120(dot)ihs(dot)com>,
"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:

> On Tue, 2 Mar 2004, [UTF-8] Paulovič Michal wrote:
>> how you solve the problem with multilevel autoicrement?
>>
>> In MySQL you create table with col1, col2. Col 2 is AUTOICREMENT and you
>> have to create UNIQUE INDEX (Col1, Col2). If you insert to this table
>> for col1 volume 1, col2 automaticaly increase by one.
>>
>> Example:
>> Insert into table values (1);
>> Insert into table values (1);
>> Insert into table values (2);
>> Insert into table values (1);
>> Insert into table values (2);

> I did this in MySQL and got this:

> create table test (id1 int, id2 int auto_increment, primary key(id2));
> Query OK, 0 rows affected (0.00 sec)

mysql> alter table test add unique index (id1, id2);
> Query OK, 0 rows affected (0.09 sec)
> Records: 0 Duplicates: 0 Warnings: 0

You can't have a multi-level autoincrement if you make the second
level unique. Use the following instead:

create table test (id1 int, id2 int auto_increment, primary key(id1,id2));

Note that this trick works only for the MyISAM and BDB table types,
not for InnoDB.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Paulovič Michal 2004-03-03 17:07:56 Re: Moving from MySQL to PGSQL....some questions (multilevel
Previous Message Palle Girgensohn 2004-03-03 16:28:13 Re: [ANNOUNCE] PostgreSQL 7.3.6 Now Available ...