Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of msatoor@gmail.com designates
 209.85.212.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53D7B868.8030307@oracle.com>
References: <53D7B868.8030307@oracle.com>
Date: Tue, 29 Jul 2014 14:53:31 -0700
Message-ID: 
 <CAFy7pk815cur_m=D_6mKmioy-SuVYmv-cG2U-6k8Xjy-7MgUDg@mail.gmail.com>
Subject: Re: renaming a referenced table
From: Mamta Satoor <msatoor@gmail.com>
To: Derby Development <derby-dev@db.apache.org>
Content-Type: multipart/alternative; boundary=f46d041826f6082ddf04ff5c1243

--f46d041826f6082ddf04ff5c1243
Content-Type: text/plain; charset=UTF-8

Hi Rick,

I looked through the original functional spec and see a mention of this
limitation but the reason is not explained. I unfortunately do not have old
emails anymore where they may have been discussions about it. Talked to
Mike on this briefly and his guess was that may be at that time in
Cloudscape's life cycle, we were more focused on getting easy functionality
out quick or may be there were catalogs referencing things by name rather
than uuid and thus making the complete implementation harder.

So, not really sure why this restriction was put in place.

thanks,
Mamta


On Tue, Jul 29, 2014 at 8:06 AM, Rick Hillegas <rick.hillegas@oracle.com>
wrote:

> I am working on a patch (DERBY-6672) which lifts the following limitation
> in Derby: you can't RENAME a table referenced by a foreign key. The
> limitation seems to go back at least as far as Cloudscape 5.1 but not as
> far back as Cloudscape 3.5 (which doesn't have a RENAME TABLE command). I
> don't have access to the code archaeology for this limitation. Could
> someone with access to the code archaeology help me understand the
> motivation for this limitation? I don't want to remove this limitation if
> it is going to cause some known edge-case to fail.
>
> Thanks,
> -Rick
>

--f46d041826f6082ddf04ff5c1243
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Rick,</div><div>=C2=A0</div><div>I looked through =
the original functional spec and see a mention of this limitation=C2=A0but =
the=C2=A0reason is not explained. I unfortunately do not have old emails an=
ymore where they may have been discussions about it. Talked to Mike on this=
 briefly and his guess was that may be at that time in Cloudscape&#39;s lif=
e cycle, we were more focused on getting easy functionality out quick or ma=
y be there were catalogs referencing things by name rather than uuid and th=
us making the complete=C2=A0implementation harder. </div>
<div>=C2=A0</div><div>So, not really sure why this restriction was put in p=
lace.</div><div>=C2=A0</div><div>thanks,</div><div>Mamta</div></div><div cl=
ass=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Jul 29, 2014=
 at 8:06 AM, Rick Hillegas <span dir=3D"ltr">&lt;<a href=3D"mailto:rick.hil=
legas@oracle.com" target=3D"_blank">rick.hillegas@oracle.com</a>&gt;</span>=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I am working on a patch (DERBY-6672) which l=
ifts the following limitation in Derby: you can&#39;t RENAME a table refere=
nced by a foreign key. The limitation seems to go back at least as far as C=
loudscape 5.1 but not as far back as Cloudscape 3.5 (which doesn&#39;t have=
 a RENAME TABLE command). I don&#39;t have access to the code archaeology f=
or this limitation. Could someone with access to the code archaeology help =
me understand the motivation for this limitation? I don&#39;t want to remov=
e this limitation if it is going to cause some known edge-case to fail.<br>

<br>
Thanks,<br>
-Rick<br>
</blockquote></div><br></div>

--f46d041826f6082ddf04ff5c1243--