Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
From: Knut Anders Hatlen <knut.hatlen@oracle.com>
To: derby-user@db.apache.org
Subject: Re: SQLException - Column 'COLUMN2' is either not in any table in the
 FROM list or appears within a join specification and is outside the scope of
 the join specification .....
References: 
 <3E6DF46E67210942B7919419E636D02914AA5142FC@TUS1XCHEVSPIN34.SYMC.SYMANTEC.COM>
	<3E6DF46E67210942B7919419E636D02914AA514306@TUS1XCHEVSPIN34.SYMC.SYMANTEC.COM>
Mail-Followup-To: derby-user@db.apache.org
Date: Thu, 24 Feb 2011 22:06:12 +0100
In-Reply-To: 
 <3E6DF46E67210942B7919419E636D02914AA514306@TUS1XCHEVSPIN34.SYMC.SYMANTEC.COM>
	(Sameer Mehta's message of "Thu, 24 Feb 2011 11:18:02 -0800")
Message-ID: <x6pqqh16t7.fsf@oracle.com>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (usg-unix-v)
MIME-Version: 1.0
Content-Type: text/plain

Sameer Mehta <Sameer_Mehta@symantec.com> writes:

> Hello All, 
>
> I found a workaround to this issue i.e. using comma "," as a delimiter
> instead of a pipe. Is this a known issue for CALL
> SYSCS_UTIL.SYSCS_IMPORT_DATA stored procedure ? Or which are valid
> delimiters to SYSCS_UTIL.SYSCS_IMPORT_DATA ?

Hi Sameer,

I'm not aware of any bug that prevents using '|' as a delimiter. In
fact, I just created a file with fields separated by pipes and called
SYSCS_IMPORT_DATA, and it worked fine for me.

If you have a test case that you can share and that shows this problem,
it would be great if you could file a bug report at
https://issues.apache.org/jira/browse/DERBY and upload the test case.

Thanks,
-- 
Knut Anders