[jira] Assigned: (DERBY-452) Import/export fails for DECIMAL type in J2ME/Foundation

[ http://issues.apache.org/jira/browse/DERBY-452?page=all ] Kathey Marsden reassigned DERBY-452: Assign To: Deepa Remesh > Import/export fails for DECIMAL type in J2ME/Foundation > --- > >

[jira] Commented: (DERBY-668) SysInfo can give misleading information when JDBC jars are loaded from jre/lib/ext

[ http://issues.apache.org/jira/browse/DERBY-668?page=comments#action_12359011 ] Bryan Pendleton commented on DERBY-668: --- Hi Andrew, Thanks for reviewing my changes. Your point about the Windows file syntax is a really good one, and I think it's wort

[jira] Commented: (DERBY-736) "" does not work as a userid for Derby client (SqlException: userid length, 0, is not allowed.)

[ http://issues.apache.org/jira/browse/DERBY-736?page=comments#action_12358993 ] Kathey Marsden commented on DERBY-736: -- This was an issue from a user who said that this was working on embedded but not for client. If enabled for client, the userid wo

[jira] Updated: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

[ http://issues.apache.org/jira/browse/DERBY-239?page=all ] Suresh Thalamati updated DERBY-239: --- Attachment: onlinebackup1.html minor updates to the spec: - Procedure can not be overloaded with different number of arguments in Derby. Added the key

[jira] Commented: (DERBY-736) "" does not work as a userid for Derby client (SqlException: userid length, 0, is not allowed.)

[ http://issues.apache.org/jira/browse/DERBY-736?page=comments#action_12358989 ] Satheesh Bandaram commented on DERBY-736: - Do we really want to allow this? How would authentication work, if enabled? What is the default schema for this "" user? >

Re: Any one else seeing lang/dcl.sql test failure ...

Suresh Thalamati wrote: > lang/dcl.sql is failing with following error message in my clients. > From the message looks , jar signing expired or some thing like that. > Any one else seeing this failure or my client is messed up ? > > >> ERROR 42X51: The class > 'org.apache.derbyTesting.databasecl

Any one else seeing lang/dcl.sql test failure ...

lang/dcl.sql is failing with following error message in my clients. From the message looks , jar signing expired or some thing like that. Any one else seeing this failure or my client is messed up ? > ERROR 42X51: The class 'org.apache.derbyTesting.databaseclassloader.emc' does not exist or is

[jira] Commented: (DERBY-668) SysInfo can give misleading information when JDBC jars are loaded from jre/lib/ext

[ http://issues.apache.org/jira/browse/DERBY-668?page=comments#action_12358985 ] Andrew McIntyre commented on DERBY-668: --- Hi Bryan, I took a look at version 3 of your patch. It looks good, just a couple comments: - On Windows you get a leading slash

[jira] Created: (DERBY-737) SYSCS_UTIL.SYSCS_COMPRESS_TABLE should create statistics if they do not exist

SYSCS_UTIL.SYSCS_COMPRESS_TABLE should create statistics if they do not exist - Key: DERBY-737 URL: http://issues.apache.org/jira/browse/DERBY-737 Project: Derby Type: Improvement Component

[jira] Created: (DERBY-736) "" does not work as a userid for Derby client (SqlException: userid length, 0, is not allowed.)

"" does not work as a userid for Derby client (SqlException: userid length, 0, is not allowed.) Key: DERBY-736 URL: http://issues.apache.org/jira/browse/DERBY-736 Project: Derb

[jira] Updated: (DERBY-668) SysInfo can give misleading information when JDBC jars are loaded from jre/lib/ext

[ http://issues.apache.org/jira/browse/DERBY-668?page=all ] Bryan Pendleton updated DERBY-668: -- Attachment: derby-668-3.diff Hi Kathey, please consider this most recent patch. I've reverted the handling of db2jcc_license_c.jar back to the pre-patch beh

Re: [jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

I got this too, I was pretty sure it was that junit is trying to read system properties, the first one being "user.dir". I think it also then tries to read Junit properties out of the user's home directory? I spent some time trying to modify the test harness to indicate where the third party

Re: [doc] fop-0.90alpha1

On 11/30/05, scott hutinger <[EMAIL PROTECTED]> wrote: > javax.xml.transform.TransformerException: > org.apache.fop.apps.FOPException: > file:///home/srh/src/derby-d/doc/trunk/fop-0.90alpha1/../out/tuning/tuningderby.fo:3:44: > Error(3/44): No element mapping definition found for fox:outline > From

Re: Issue type for test bugs

On 11/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Myrna van Lunteren <[EMAIL PROTECTED]> writes: > On 11/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi, which Jira issue type, "test" or "bug", should be used when reporting a >> bug>> in a test? -->> dt>>> I've been

[jira] Closed: (DERBY-280) Wrong result from select when aliasing to same name as used in group by

[ http://issues.apache.org/jira/browse/DERBY-280?page=all ] Rick Hillegas closed DERBY-280: --- The regression test for this patch (in aggregate.sql) succeeds. So I am closing this bug. > Wrong result from select when aliasing to same name as used in group

[jira] Resolved: (DERBY-280) Wrong result from select when aliasing to same name as used in group by

[ http://issues.apache.org/jira/browse/DERBY-280?page=all ] Rick Hillegas resolved DERBY-280: - Resolution: Incomplete I am resolving this bug as Incomplete. The complete fix to this bug is part of the cleanup described in jira 681. > Wrong result

Re: [jira] Commented: (DERBY-280) Wrong result from select when aliasing to same name as used in group by

There was a reported of a possible NPE in a particular code path and condition which Satheesh identified - I remember Rick fixing it and re-running the tests...On 11/30/05, Kathey Marsden (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-280?page=comments#acti

[jira] Commented: (DERBY-280) Wrong result from select when aliasing to same name as used in group by

[ http://issues.apache.org/jira/browse/DERBY-280?page=comments#action_12358945 ] Kathey Marsden commented on DERBY-280: -- In an earlier comment you mentioned a valid query which worked before the patch which now fails with: ij> select a+1 as a, a+1 as

[jira] Created: (DERBY-735) Need implementation for `ON UPDATE CASCADE`

Need implementation for `ON UPDATE CASCADE` Key: DERBY-735 URL: http://issues.apache.org/jira/browse/DERBY-735 Project: Derby Type: New Feature Components: SQL Versions: 10.1.2.1 Environment: Gentoo Linux, JD

Re: [jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

Daniel John Debrunner <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> Daniel John Debrunner <[EMAIL PROTECTED]> writes: > >>>Why do you need to grant permissions to read all files for the >>>derbyTesting and junit jars? >> >> >> I'm sorry, but I think you need to ask the junit develope

[jira] Updated: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.

[ http://issues.apache.org/jira/browse/DERBY-310?page=all ] Kathey Marsden updated DERBY-310: - type: Improvement (was: Bug) > Document and/or change Derby client code to match behavior with Embedded > driver where possible. > --

[jira] Updated: (DERBY-734) lang/closed.java fails in 50% of runs

[ http://issues.apache.org/jira/browse/DERBY-734?page=all ] Dyre Tjeldvoll updated DERBY-734: - type: Bug (was: Test) > lang/closed.java fails in 50% of runs > - > > Key: DERBY-734 > URL: http://issue

Re: Issue type for test bugs

Myrna van Lunteren <[EMAIL PROTECTED]> writes: > On 11/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> which Jira issue type, "test" or "bug", should be used when reporting a >> bug >> in a test? >> >> -- >> dt >> >> >> > I've been using bug, then component test, because the te

[jira] Updated: (DERBY-297) Submit an entry for the Derby logo contest by uploading it to this issue

[ http://issues.apache.org/jira/browse/DERBY-297?page=all ] Roger Dudler updated DERBY-297: --- Attachment: roger_full_showcase.jpg roger_full_showcase.jpg shows variants for the derby_logo_only.jpg Hope you like it. > Submit an entry for the Derby logo con

Re: [jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

[EMAIL PROTECTED] wrote: > Daniel John Debrunner <[EMAIL PROTECTED]> writes: >>Why do you need to grant permissions to read all files for the >>derbyTesting and junit jars? > > > I'm sorry, but I think you need to ask the junit developers about > that. I don't know exactly which files junit wan

[jira] Commented: (DERBY-280) Wrong result from select when aliasing to same name as used in group by

[ http://issues.apache.org/jira/browse/DERBY-280?page=comments#action_12358935 ] Satheesh Bandaram commented on DERBY-280: - What regression? I don't know of any regression introduced by this patch. Let me know if there is one. RICK, assuming there

[jira] Updated: (DERBY-469) Unnecessary if block in the FromBaseTable.bindTableDescriptor() method

[ http://issues.apache.org/jira/browse/DERBY-469?page=all ] Kathey Marsden updated DERBY-469: - type: Task (was: Bug) I am changing this to task because I think it is just a code cleanup and not a bug. Hopefully Task is the correct category. > Unneces

Re: [doc] fop-0.90alpha1 - avalon jar version?

Guess this is the fop-0.20.5 stuff in the lib/ sorry for the noise, scott scott hutinger wrote: Anyone know the status of the following doc...lib/ file? avalon-framework-cvs-20020806.jar Manifest-Version: 1.0 Created-By: Apache Ant 1.5 Extension-Name: avalon-framework Specification-Vendor: Apac

Re: [jira] Created: (DERBY-734) lang/closed.java fails in 50% of runs

With timing types of bugs it often helps to mention the hardware you are running on, especially if the test has any sort of threading. Often number of processors/speed of processors is the cause - and often as you have labeled it, it is a test problem (rather than a code issue) not expecting th

Re: Issue type for test bugs

On 11/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi,which Jira issue type, "test" or "bug", should be used when reporting a bug in a test?--dt   I've been using bug, then component test, because the tests/test harness can have/need improvements, bugs, wishes...   But maybe I've been wrong

[jira] Commented: (DERBY-280) Wrong result from select when aliasing to same name as used in group by

[ http://issues.apache.org/jira/browse/DERBY-280?page=comments#action_12358932 ] Kathey Marsden commented on DERBY-280: -- I was wondering was there another bug filed for the regression introduced by the patch? I did not see one linked to this issue.

Re: [jira] Commented: (DERBY-733) Starvation in RAFContainer.readPage()

It should be possible to build a 1.5 specific solution, though Bryan has not succeeded yet in getting the build side of the solution to work. Of course such a solution will only make 1.5 and future versions go faster. In general I think it is better to use the native java support if possible, bu

Re: [jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

I think the properties file stuff needs re-written in the JVM. It's not very user friendly! :-) But, I don't have any better suggestions. I was messing around with that for a while, and gave up in disgust. One can't control it's search from my limited experience. So I don't think it's the

Re: [jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

Daniel John Debrunner <[EMAIL PROTECTED]> writes: > Dyre Tjeldvoll (JIRA) wrote: > >> [ http://issues.apache.org/jira/browse/DERBY-85?page=all ] >> >> Dyre Tjeldvoll updated DERBY-85: >> >> >> Attachment: derby-85.diff >> derby-85.stat >>

[doc] fop-0.90alpha1 - avalon jar version?

Anyone know the status of the following doc...lib/ file? avalon-framework-cvs-20020806.jar Manifest-Version: 1.0 Created-By: Apache Ant 1.5 Extension-Name: avalon-framework Specification-Vendor: Apache Software Foundation Specification-Version: 1.0 Implementation-Vendor: Apache Software Foundation

Re: Derby on GCJ

--- Knut Anders Hatlen <[EMAIL PROTECTED]> wrote: > craig vanderborgh <[EMAIL PROTECTED]> writes: > > > Hello, > > > > We are going to make a substantial attempt to get Derby running on GCJ. > The > > goal is not to run Derby on the GCJ "JVM", but instead to ahead-of-time > compile > > all the

Re: [jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

Dyre Tjeldvoll (JIRA) wrote: > [ http://issues.apache.org/jira/browse/DERBY-85?page=all ] > > Dyre Tjeldvoll updated DERBY-85: > > > Attachment: derby-85.diff > derby-85.stat > derbyall_report.txt > > New patch with Junit

[doc] fop-0.90alpha1

Just for everyone; FOP has as of last week, a new re-write of fop. It's pretty much a re-write, I have been tracking the source for quite a few months off and on, and would highly recommend moving to this version when it will build. (besides the other 'out of memory' problem). Also, for some

[jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

[ http://issues.apache.org/jira/browse/DERBY-85?page=all ] Dyre Tjeldvoll updated DERBY-85: Attachment: (was: Bugs.java) > NPE when creating a trigger on a table and default schema doesn't exist. >

[jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

[ http://issues.apache.org/jira/browse/DERBY-85?page=all ] Dyre Tjeldvoll updated DERBY-85: Attachment: (was: derby-85-notabs.diff) > NPE when creating a trigger on a table and default schema doesn't exist. > -

[jira] Updated: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

[ http://issues.apache.org/jira/browse/DERBY-85?page=all ] Dyre Tjeldvoll updated DERBY-85: Attachment: derby-85.diff derby-85.stat derbyall_report.txt New patch with Junit test case. Note that I had to modify the Securit

[jira] Created: (DERBY-734) lang/closed.java fails in 50% of runs

lang/closed.java fails in 50% of runs - Key: DERBY-734 URL: http://issues.apache.org/jira/browse/DERBY-734 Project: Derby Type: Test Components: Test Environment: java version "1.5.0_01" Java(TM) 2 Runtime Environment, Standar

[jira] Commented: (DERBY-733) Starvation in RAFContainer.readPage()

[ http://issues.apache.org/jira/browse/DERBY-733?page=comments#action_12358925 ] Knut Anders Hatlen commented on DERBY-733: -- I have tried to put calls to the lock() and unlock() methods in the Java 1.5 ReentrantLock class around the synchronized blo

[jira] Created: (DERBY-733) Starvation in RAFContainer.readPage()

Starvation in RAFContainer.readPage() - Key: DERBY-733 URL: http://issues.apache.org/jira/browse/DERBY-733 Project: Derby Type: Bug Components: Performance, Store Versions: 10.2.0.0, 10.1.2.1, 10.1.3.0, 10.1.2.2 Enviro

Issue type for test bugs

Hi, which Jira issue type, "test" or "bug", should be used when reporting a bug in a test? -- dt

Re: Adding a class to a jar file programatically

Yes, I could do that, it's just that the jar file I want to add to is kind of big and I wanted to avoid the overhead. I guess I need to do the copy/rename approach. David Bryan Pendleton wrote: Oh, I see I misunderstood the question. I think in the past I have always made a copy of the jar

[jira] Updated: (DERBY-732) ERROR XBCM1: Java linkage error thrown during load of generated class for query with large number of logical operators and substitution parameters.

[ http://issues.apache.org/jira/browse/DERBY-732?page=all ] Kathey Marsden updated DERBY-732: - Attachment: TestConnect.java Attached program reproduces the problem In ij connect 'wombat;create=true'; create table t1 (ITEMID int, VERSIONID int); java Te

[jira] Created: (DERBY-732) ERROR XBCM1: Java linkage error thrown during load of generated class for query with large number of logical operators and substitution parameters.

ERROR XBCM1: Java linkage error thrown during load of generated class for query with large number of logical operators and substitution parameters.

Re: Derby on GCJ

craig vanderborgh <[EMAIL PROTECTED]> writes: > Hello, > > We are going to make a substantial attempt to get Derby running on GCJ. The > goal is not to run Derby on the GCJ "JVM", but instead to ahead-of-time > compile > all the Derby sources (to .o files using the gcj compiler) so that the resu

Re: Derby on GCJ

craig vanderborgh <[EMAIL PROTECTED]> writes: > Hello, > > We are going to make a substantial attempt to get Derby running on GCJ. The > goal is not to run Derby on the GCJ "JVM", but instead to ahead-of-time > compile > all the Derby sources (to .o files using the gcj compiler) so that the resu

Re: Native Derby?

Steve Stewart <[EMAIL PROTECTED]> writes: > Hi folks, > > Whether it was UCSD Pascal, Java, or whatever, I never much > liked the idea of virtual machines hogging memory and > intermediate bytecode being compiled every time it executes. I know what you mean, and I understand your concern. Having

[jira] Commented: (DERBY-649) Useful indexes not used in UNION ALL

[ http://issues.apache.org/jira/browse/DERBY-649?page=comments#action_12358885 ] Satheesh Bandaram commented on DERBY-649: - I am trying to address this problem by trying to push predicates into UNION. For now, I am not handling the cases where the s