Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread EDBMan b6
Fri, Jan 26 2007 9:17 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim

I have no idea how I've achieved this but I managed to create two tables with the same name in one database!

Roy Lambert
Fri, Jan 26 2007 1:57 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< I have no idea how I've achieved this but I managed to create two tables
with the same name in one database! >>

Are you sure about this ?  I can't think of any way in which that would be
possible short of a bug in the alteration that was renaming the tables
incorrectly.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Jan 26 2007 2:03 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


I'm guessing that's what it was, which one I have no idea I've managed to screw up so many times this afternoon!

Roy Lambert
Fri, Jan 26 2007 6:30 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< I'm guessing that's what it was, which one I have no idea I've managed to
screw up so many times this afternoon! >>

Is it possible that what you saw was a duplicate table name in the left
treeview ?  IOW, did you try to create the same table twice ?  In such a
case it may be possible due to an interface refresh that the duplicate name
was picked up in the treeview after the create failed with an error that the
table already exists.

I've gone through the code thoroughly today and it's just basically
impossible to have a duplicate table name in a database catalog.  Any time
you tried to load such a database catalog, EDB would give you an error
saying that there was a duplicate table name present.  It's an intrinsic
part of the catalog load and validation process, all of which is done to
prevent anyone from using an invalid or corrupted catalog.  Any addition of
a table object goes through the same check, so even if EDB wanted to it
couldn't bypass this check.  It's in a separate part of the code base from
the creation and alteration and neither of these operations can override it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sat, Jan 27 2007 4:03 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


The duplicate was definitely on the right hand side (might have been on the left side as well but can't swear to that) and memory (fallible) says that the two of them were there even after closing and starting EBDMan.

If I ever manage to replicate it I'l try harder to remember what I did.

Roy Lambert
Sat, Jan 27 2007 10:47 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< The duplicate was definitely on the right hand side (might have been on
the left side as well but can't swear to that) and memory (fallible) says
that the two of them were there even after closing and starting EBDMan. >>

That's what is hard to understand.  As I said before, there's really no way
that EDB will load a catalog with duplicate table names.  You can't even
have a view and a table with the same name.

Do you remember after which operation the duplicate table showed up ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Sat, Jan 27 2007 11:22 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


Sorry no. The best I can say is some sort of table alteration / error combo or a sequence of such.

I'll probably never see it again either Smiley

Roy Lambert
Sat, Jan 27 2007 11:34 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< I'll probably never see it again either Smiley>>

Well, I hope that's the case. Wink

--
Tim Young
Elevate Software
www.elevatesoft.com

Image