Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <437CF0A2.3090507@Sourcery.Org>
Date: Thu, 17 Nov 2005 13:05:38 -0800
From: Satheesh Bandaram <satheesh@Sourcery.Org>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: UpdateNode/DeleteNode and SYNONYM
References: <437CE814.90305@debrunners.com>
In-Reply-To: <437CE814.90305@debrunners.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

It may be possible to differ this synonym resolution to
verifyTargetTable(), but this is currently called after some cursor bind
checking that expects correct target table name. If verifyTargetTable()
can be performed before this cursor checking, which resolves synonyms
correctly, the following code can be removed.

Satheesh

Daniel John Debrunner wrote:

>I was fixing some code in the bind() for UpdateNode and DeleteNode for
>DERBY-571 and noticed that the methods are very similar and possibly
>could be combined.
>
>One thing that stood out is that UpdateNode has this code at the
>beginning of bind() related to SYNONYMs
>
>		// check if targetTable is a synonym
>		if (targetTableName != null)
>		{
>			TableName synonymTab = resolveTableToSynonym(this.targetTableName);
>			if (synonymTab != null)
>				this.targetTableName = synonymTab;
>		}
>
>DeleteNode does not have this code.
>
>However, both nodes call verifyTargetTable(), which also performs the
>same SYNONYM lookup.
>
>Is the code in UpdateNode required, or is it just left over from the
>implementation by mistake?
>
>Any ideas?
>Dan.
>
>
>
>  
>