db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yip Ng" <yipng...@gmail.com>
Subject Re: [jira] Commented: (DERBY-1784) When qualifying a column name with its synonym name in the select list, Derby throws SQLSTATE 42X04.
Date Tue, 19 Sep 2006 17:20:24 GMT
Hi Myrna:

   Thanks for the info.  I am running the 10.1 derbyall suite on Sun JDK
1.4.2_12 Windows XP Pro SP2 environment.  I usually run my patches on trunk
and I have never seen these diffs in the trunk code line before.  So I was
abit surprised to see diffs on a *clean* 10.1 codeline.  My CLASSPATH have
always list derby.jar as the first jar entry followed by derbyclient.jar,
derbynet.jar, derbytools.jar, etc.

Yip

On 9/19/06, Myrna van Lunteren <m.v.lunteren@gmail.com> wrote:
>
> On 9/18/06, Yip Ng (JIRA) <derby-dev@db.apache.org> wrote:
> >    [
> http://issues.apache.org/jira/browse/DERBY-1784?page=comments#action_12435625]
> >
> > Yip Ng commented on DERBY-1784:
> > -------------------------------
> >
> > I ran derbyall against a *clean* 10.1 build and the following tests
> failed:
> >
> > derbyall/derbyall.fail:unit/T_Diagnosticable.unit
> > derbyall/derbyall.fail:i18n/urlLocale.sql
> > derbyall/derbyall.fail:i18n/messageLocale.sql
> > derbyall/derbyall.fail:i18n/iepnegativetests_ES.sql
> > derbyall/derbynetclientmats/derbynetmats.fail:derbynet/sysinfo.java
> > derbyall/derbynetmats/derbynetmats.fail:derbynet/sysinfo.java
> >
> > Are these tests known issues in 10.1?  I ran derbyall again with the
> patch and got the same result, so the patch didn't cause these failures.
> >
> Hi Yip,
>
> All these I have seen failing in the past, but there may be set-up
> issues around it too.
> Just checking - what was your jvm and OS when you ran these? If ibm's
> jvm on Linux, you may need to check on the environment setting for
> $LANG - it may need to be en_US (instead of the os default
> en_US.UTF8).
> Re sysinfo failures - check on the sequence of the jars, i.e. put
> derby.jar first, then derbytools.jar, then the rest, and see if the
> test passes. (there was a bug that got fixed in later releases).
> re T_Diagnoticable...I think this intermittent failure was hoped to be
> fixed (see DERBY-496)...
>
> It seems to me you've been running into these failures with other
> patches, correct?
>
> Myrna
>

Mime
View raw message