Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Table definition w/FK fails
Fri, Jan 5 2007 10:36 PMPermanent Link

"Ole Willy Tuv"
Statement 1)

create table t1
(
 c1 integer,
 constraint pk_t1 primary key (c1)
)

Statement 2)

create table t2
(
 c1 integer,
 c2 integer,
 constraint pk_t2 primary key (c1),
 constraint fk_t2_c2 foreign key (c2) references t1 (c1)
)

Error:

ElevateDB Error #401 The table 0 does not exist

Ole Willy Tuv

Sat, Jan 6 2007 11:27 AMPermanent Link

"David Farrell-Garcia"
>  constraint fk_t2_c2 foreign key (c2) references t1 (c1)
> )
>
> Error:
>
> ElevateDB Error #401 The table 0 does not exist
>
> Ole Willy Tuv

I haven't tried it yet in SQL but I am having trouble doing it in the
EDBMgr.  Anyway, don't you have to reference the target contstraing by
name rather then the field in EDB?



--
David Farrell-Garcia
Whidbey Island Software, LLC
Mon, Jan 8 2007 4:17 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Ole,

<< Error:

ElevateDB Error #401 The table 0 does not exist >>

Fixed.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Jan 10 2007 11:28 AMPermanent Link

"Ole Willy Tuv"
Tim,

> Fixed.

There seems to be a problem with the RI checking.

After creating the tables, I executed the following statement:

drop table t1

The statement executed without any error regarding the dependancy. After
that I was getting AVs when refreshing or closing/opening the database. I
then closed and reopened both the server and the ElevateDB Manager. When
opening the database, I got the following error:

ElevateDB Error #401 The table 224 does not exist.

Ole Willy Tuv

Wed, Jan 10 2007 5:57 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Ole,

<< There seems to be a problem with the RI checking.

After creating the tables, I executed the following statement:

drop table t1

The statement executed without any error regarding the dependancy. After
that I was getting AVs when refreshing or closing/opening the database. I
then closed and reopened both the server and the ElevateDB Manager. When
opening the database, I got the following error:

ElevateDB Error #401 The table 224 does not exist. >>

I'll check it out.  It sounds like the dependency checking on drops isn't
getting fired off for some reason.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Jan 10 2007 7:04 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Ole,

Yep, that was it.  We had the checks in there, but the tables weren't
calling them and were letting them go by.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image