Thread: Re: [INTERFACES] Re: more odbc patches

Re: [INTERFACES] Re: more odbc patches

From
Cedar Cox
Date:
I don't get it.  Does this mean the ODBC driver is checking referential
integrity before it passes things to the backend server?  Seems kind of
pointless to me.  I thought the ODBC driver just passes through RI errors
generated by the backend.

-Cedar

On Tue, 23 Jan 2001, Max Khon wrote:

> hi, there!
>
> On Mon, 22 Jan 2001, Bruce Momjian wrote:
>
> > Can someone comment on this?
>
> I have got more comments from Constantin: current implementation will fail
> (return too many rows) if one table has two foreign keys, e.g.:
> CREATE TABLE prim(i integer PRIMARY KEY);
> CREATE TABLE f(i integer REFERENCES prim, j integer REFERENCES prim);


Re: [INTERFACES] Re: more odbc patches

From
Max Khon
Date:
hi, there!

On Tue, 23 Jan 2001, Cedar Cox wrote:

> I don't get it.  Does this mean the ODBC driver is checking referential
> integrity before it passes things to the backend server?  Seems kind of
> pointless to me.  I thought the ODBC driver just passes through RI errors
> generated by the backend.

we talk about SQLForeignKeys functionality :)
it has nothing to do with RI errors reporting

> On Tue, 23 Jan 2001, Max Khon wrote:
>
> > hi, there!
> >
> > On Mon, 22 Jan 2001, Bruce Momjian wrote:
> >
> > > Can someone comment on this?
> >
> > I have got more comments from Constantin: current implementation will fail
> > (return too many rows) if one table has two foreign keys, e.g.:
> > CREATE TABLE prim(i integer PRIMARY KEY);
> > CREATE TABLE f(i integer REFERENCES prim, j integer REFERENCES prim);

/fjoe