Stephan Szabo <[EMAIL PROTECTED]> writes:
>> In fact, there's a good argument that we should require the two columns
>> to have the exact same datatype.
> I think the spec only requires them to be comparable
Oh, in that case never mind ... but I'd still favor checking for
existence of the compar
On Tue, 12 Dec 2000, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> >> In fact, there's a good argument that we should require the two columns
> >> to have the exact same datatype.
>
> > I think the spec only requires them to be comparable
>
> Oh, in that case never mind ... but
On Tue, 12 Dec 2000, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> >> 2) It should be error in *creation* of table if there is no comparasion
> >> operator for constrain check
>
> > Possibly, although it currently doesn't to allow you to add the operator
> > after you do the ref
Stephan Szabo <[EMAIL PROTECTED]> writes:
>> 2) It should be error in *creation* of table if there is no comparasion
>> operator for constrain check
> Possibly, although it currently doesn't to allow you to add the operator
> after you do the references. The benefits of that might be outweighed
> Hi.
>
> I use version from cvs.
>
> I want to have array of referencies to another table, so I do:
> cms=# create table a (a int primary key); create table b (b int[]
> references a);
> NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'a_pkey' for
> table 'a'
> CREATE
> NOTICE:
Hi.
I use version from cvs.
I want to have array of referencies to another table, so I do:
cms=# create table a (a int primary key); create table b (b int[]
references a);
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'a_pkey' for
table 'a'
CREATE
NOTICE: CREATE TABLE will create
