Re: Moving from MySQL to PGSQL....some questions (multilevel - Mailing list pgsql-general

From Paulovič Michal
Subject Re: Moving from MySQL to PGSQL....some questions (multilevel
Date
Msg-id 40462592.2070407@paulovic.sk
Whole thread Raw
In response to Re: Moving from MySQL to PGSQL....some questions (multilevel  (Bruno Wolff III <bruno@wolff.to>)
List pgsql-general
Bruno Wolff III wrote:

>On Wed, Mar 03, 2004 at 18:12:18 +0100,
>  Paulovi?? Michal <michal@paulovic.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.
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
>    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>
>________ Information from NOD32 ________
>This message was checked by NOD32 Antivirus System for Linux Mail Server.
>http://www.nod32.com
>
>
>
Yes, :(
I have thought about this issue. Upgrade of PgSQL might by first step -
probably.
In other node at this formu other colegue give me an idea but it works
on 7.2 and newer.........
Yes – I have to try negotiate with provider of my DB enviroment for
upgrading version of PgSQL.

tnx a lot for all



pgsql-general by date:

Previous
From: Nick Barr
Date:
Subject: Re: Mistake in my query or Index Scan on subquery failure?
Next
From: Eric Davies
Date:
Subject: gist index build produces corrupt result on first access to table.