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

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Paulovi?? Michal <michal(at)paulovic(dot)sk>
Cc: Harald Fuchs <hf118(at)protecting(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Moving from MySQL to PGSQL....some questions (multilevel
Date: 2004-03-03 17:48:20
Message-ID: 20040303174820.GA24874@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Mar 03, 2004 at 18:12:18 +0100,
Paulovi?? Michal <michal(at)paulovic(dot)sk> wrote:
> You don't build secent level unique
> You have to create uniqe index under both levels (first and second)
> together. But in MySQL there is no problem.
> I alredy have table with mulitlevel autoincrement (in MySQL) but now I
> want move this to PostgreSQL 7.1, and i have problem with this. It
> doesn't work :-((((

That isn't an appropiate use of sequences. You should only be using
their uniqeness. If the values are supposed to have some other semantics
you should be using another mechanism.

Also Posgtesql 7.1 is very old. You really should upgrade to something
more recent. 7.4.2 is due out in a few days.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nick Barr 2004-03-03 18:03:41 Re: Mistake in my query or Index Scan on subquery failure?
Previous Message Gellert, Andre 2004-03-03 17:17:06 Mistake in my query or Index Scan on subquery failure? (7.4)