From: | Stéphane Chomat <steph_chomat(at)mac(dot)com> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Primary key with oid + name : error, which solution ? |
Date: | 2001-10-31 22:21:25 |
Message-ID: | 9F2CCC32-CE4D-11D5-9FB4-003065C28650@mac.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Yes, name is an internal type. The problem is in the type of the table
repertory. If it is not
possible to use this syntaxe, i will take the type char. I just try the
new possibility of postgressql.
thanks.
steph.
Le mercredi 31 octobre 2001, à 11:08 , Stephan Szabo a écrit :
> On Wed, 31 Oct 2001, [ISO-8859-1] Stéphane Chomat wrote:
>
>> I create two table repertory and person. And i have an error :
>>
>>> CREATE TABLE repertory (name_rep name, attribut text[], PRIMARY
>> KEY(name_rep));
>>> CREATE TABLE person (nam_rep repertory, name_pers text, url text, eadr
>> text, tel text, attribut text[], PRIMARY KEY(name_pers,nam_rep));
>>
>> NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index
>> 'person_pkey'
>> for table 'person'
>> ERROR: DefineIndex: type repertory has no default operator class
>>
>> which solution for this problem ?
>
> You'd probably be best off using the name of the repertory in the person
> table along with a foreign key. Also, IIRC name is mostly meant as an
> internal type. You probably really want varchar(<length>).
>
>
Stéphane Chomat
22 rue Le Brix
38100 Grenoble
603-999-478
steph_chomat(at)mac(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-10-31 22:40:21 | Re: Primary key with oid + name : error, which solution ? |
Previous Message | Stephan Szabo | 2001-10-31 22:08:55 | Re: Primary key with oid + name : error, which solution ? |