[Auto-generated mail]
*tinderbox_trunk16* 557447/2007-07-19 03:52:41 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
4298294 089.09% derbyall
086058605 0 1986.
[
https://issues.apache.org/jira/browse/DERBY-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor reassigned DERBY-2950:
--
Assignee: Mamta A. Satoor
> BatchUpdateTest.testMinimalDDLInBatch Fails when run with c
[
https://issues.apache.org/jira/browse/DERBY-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513816
]
Mamta A. Satoor commented on DERBY-2950:
I do not think this is a bug. The exception is being thrown for foll
[
https://issues.apache.org/jira/browse/DERBY-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2656:
--
Attachment: FullCollationTests_out.txt
Attaching new test output. There was a problem with the
Myrna van Lunteren wrote:
Hi,
There was a discussion ensuing from DERBY-2896, which I think should
be a general discussion item, following mamta's check-in for a fix for
that critical issue.
Knut Anders Wrote:
>The changes in metadata.properties will not be picked up when you
upgrade from 10.
[
https://issues.apache.org/jira/browse/DERBY-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2656:
--
Attachment: (was: FullCollation.out)
> Run suites.All against a collated database
> ---
[
https://issues.apache.org/jira/browse/DERBY-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513790
]
Kathey Marsden commented on DERBY-2656:
---
I deleted FullCollation.out. There seems to be a problem with the run
[Auto-generated mail]
*tinderbox_trunk16* 557398/2007-07-18 23:12:35 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
4298294 089.35% derbyall
086058605 0 2077.
[
https://issues.apache.org/jira/browse/DERBY-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2656:
--
Attachment: FullCollation.out
Here are the results of running lang, jdbcapi and store suites on
Bryan Pendleton wrote:
In the context of https://issues.apache.org/jira/browse/DERBY-581
I've been studying the SQL-99 standard's specification of
OLAP operations:
- Feature T611 specifies "Elementary OLAP operations"
- Feature T612 specifies "Advanced OLAP operations"
I'm interested in explor
[
https://issues.apache.org/jira/browse/DERBY-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513753
]
Kathey Marsden commented on DERBY-2942:
---
Hi Ramin,
Thanks for the patch. A few minor comments:
There are a
[
https://issues.apache.org/jira/browse/DERBY-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513751
]
Kathey Marsden commented on DERBY-2941:
---
I checked the fix into the 10.3 branch as well, so hopefully the fix v
[
https://issues.apache.org/jira/browse/DERBY-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513748
]
Myrna van Lunteren edited comment on DERBY-2941 at 7/18/07 4:16 PM:
I know you ch
[
https://issues.apache.org/jira/browse/DERBY-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513748
]
Myrna van Lunteren commented on DERBY-2941:
---
I know you checked in the test to 10.3 branch, but I'm wonderi
[
https://issues.apache.org/jira/browse/DERBY-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2952:
--
Affects Version/s: (was: 11.0.0.0)
10.4.0.0
> create table from valu
create table from values clause causes error: ERROR 42ZA3: The table will have
collation type UCS_BASIC which is different than the collation of the schema
TERRITORY_BASED
[
https://issues.apache.org/jira/browse/DERBY-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513738
]
Kathey Marsden commented on DERBY-2950:
---
In CollationTest.collatedSuite, you can just add the test and import
Hi Manish, thank you very much for the encouraging words. I agree
that the more people who get familiar with the code and the
implementation, the better it is.
Regarding the SQL standard, I think the best thing I can do is
to refer you to http://en.wikipedia.org/wiki/SQL#Standardization
Also, I
[
https://issues.apache.org/jira/browse/DERBY-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513730
]
Mamta A. Satoor commented on DERBY-2950:
Kathey, I won't have time until later this evening to look into this
[
https://issues.apache.org/jira/browse/DERBY-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2951:
--
Summary: BatchUpdateTest.testAssociatedParams test fails with collation
with exception: Java ex
BatchUpdateTest.testAssociatedParams test fails with collation with exception:
java.sql.SQLException: Java exception: 'ASSERT FAILED type of inserted
column[0] = org.apache.derby.iapi.types.CollatorSQLChartype of template
column[0] = org.apache.derby.
[
https://issues.apache.org/jira/browse/DERBY-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513729
]
Mamta A. Satoor commented on DERBY-2896:
Ported the changes from main into 10.3 codeline (revision 557405) Wi
[
https://issues.apache.org/jira/browse/DERBY-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2950:
--
Component/s: SQL
> BatchUpdateTest.testMinimalDDLInBatch Fails when run with collation with
>
BatchUpdateTest.testMinimalDDLInBatch Fails when run with collation with
exception: java.sql.SQLException: Operand of LIKE predicate with type
VARCHAR(128) and collation UCS_BASIC is not compatable with LIKE pattern
operand with type CHAR(4) and collation
Myrna, I have run critical tests on my 10.3 codeline after merge and things
are running fine so far. I will go ahead and back port my changes into
10.3codeline because I will be gone for the rest of the evening and in
case we
decide to cut a 10.3.1.x branch before that. I will tackle the metadata
In my openion we should go for a release (if we can include Mamta's fix,
that will be great). But not to wait for the bugs which are not picked by
anyone. And then may be in September we can have a bugfix release. As far,
for me RC2 tests are progressing well. So nothing stops me to vote +1
Thank
Hi Myrna!
I understand your concern and would like to share my thoughts.
I think a combination of 1) and 3) would be best.
I would prefer a release now, but understand the concerns in the
community and thereby the need for a new RC. After the 26th I will also
start a vacation, so that would sui
Bryan,
It sounds like a very reasonable and thoughtful way to get started. One
thing which is frustrating about working with Derby is that large portions
of the code are so very cryptic and brittle, sometimes unnceccsarily so.
Having more than one person try and understand relevant code, document
[
https://issues.apache.org/jira/browse/DERBY-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden resolved DERBY-1806.
---
Resolution: Cannot Reproduce
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ---
[Auto-generated mail]
*tinderbox_trunk16* 557291/2007-07-18 17:22:18 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
3298295 0 169.71% derbyall
084588458 0 1832.
Hi,
There was a discussion ensuing from DERBY-2896, which I think should
be a general discussion item, following mamta's check-in for a fix for
that critical issue.
Knut Anders Wrote:
>The changes in metadata.properties will not be picked up when you upgrade from
10.3.1.x to 10.3.2.x.
Kathe
[
https://issues.apache.org/jira/browse/DERBY-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton reassigned DERBY-581:
-
Assignee: Bryan Pendleton
> Modify SQL to skip N rows of the result and return the next M
[
https://issues.apache.org/jira/browse/DERBY-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513688
]
Kathey Marsden commented on DERBY-2896:
---
>The changes in metadata.properties will not be picked up when you upg
hi all,
w.r.t DERBY-2945(convert lang/primarykey.sql to junit)
I have a small doubt.
There is a test for verifying a unique key can not contain nulls.
1)-- verify that a unique key can not contain nulls
create table pos1 (c1 int not null unique, c2 int);
insert into
On 7/18/07, Mamta A. Satoor (JIRA) <[EMAIL PROTECTED]> wrote:
Myrna, can I migrate this change to 10.3 codeline?
There was a discussion about this recently, can't find the thread
right now, but basically, I can't really stop anyone from checking
in...If the committer feels a high degree of conf
[
https://issues.apache.org/jira/browse/DERBY-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor reassigned DERBY-2940:
--
Assignee: Mamta A. Satoor
> CollationTest fail after hard upgrade from 10.2
> -
[
https://issues.apache.org/jira/browse/DERBY-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513678
]
Knut Anders Hatlen commented on DERBY-2896:
---
I haven't followed this discussion closely, but I'd just menti
[
https://issues.apache.org/jira/browse/DERBY-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513677
]
Mamta A. Satoor commented on DERBY-2940:
Oystein, I did some research into this issue. The failure in the Col
Dimple Bhatia <[EMAIL PROTECTED]> writes:
> Hi,
> I have overloaded the execute method in
> org.apache.derby.impl.jdbc.EmbedStatement.execute and can call that via a
> test program using the Embedded driver and that works fine.Now I want to run
> Derby in network server mode and want to call this
The last couple of days reports for suitesAll on Solaris x64 (sol) have
shown 'UNKNOWN'.
The JUnit test has crashed with: Exception in thread "main"
java.lang.OutOfMemoryError: PermGen space
Because of this there is no complete log from JUnit and the reporting
scripts are unable to parse them su
Thank You bryan.what a silly mistake?.In my old system I have
jdk1.4 in /usr but in new system I have it in /opt.But I have been using
the old ant.properties file.I have been struggling for the last 3 days
for the simple mistake.
n e way Thank You very much.
On Wed, 18 Jul 2007, Bryan
[EMAIL PROTECTED] ~]# echo $JAVA_HOME
/opt/java/j2sdk1.4.2_14
[EMAIL PROTECTED] ~]# echo $CLASSPATH
.:/opt/java/j2sdk1.4.2_14/lib:/opt/java/j2sdk1.4.2_14/lib/tools.jar:
/opt/java/j2sdk1.4.2_14/lib/dt.jar:/opt/java/j2sdk1.4.2_14/lib/jpda.jar:
/opt/java/j2sdk1.4.2_14/jre/lib/rt.jar:/opt/java/j2sdk1
hi all,
while I am trying to build the derby(10.3) in Fedora 7
I am getting the following problems.please help me as my two issues
DERBY-2750 and DERBY-2945 are getting delayed for the same reason.
Some sys info.
[EMAIL PROTECTED] ~]# echo $JAVA_HOME
/opt/java/j2sdk1.4.2
[
https://issues.apache.org/jira/browse/DERBY-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513643
]
Mamta A. Satoor commented on DERBY-2896:
Checked in fix for this bug in main with revision 557334. The commit
In the context of https://issues.apache.org/jira/browse/DERBY-581
I've been studying the SQL-99 standard's specification of
OLAP operations:
- Feature T611 specifies "Elementary OLAP operations"
- Feature T612 specifies "Advanced OLAP operations"
I'm interested in exploring an implementation of
[Auto-generated mail]
*Daily* 556951/2007-07-17 18:00:14 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
3298295 072.58% derbyall
084588458 0 844.34% suitesAll
sles
NA
[
https://issues.apache.org/jira/browse/DERBY-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513623
]
Mamta A. Satoor commented on DERBY-2940:
I will look into this in next hr or so after I finish checking in a
Issue Subscription
Filter: Derby: JIRA issues with patch available (10 issues)
Subscriber: derby-dev
Key Summary
DERBY-2936 Use java.nio.ByteBuffer for buffering in DDMWriter
https://issues.apache.org/jira/browse/DERBY-2936
DERBY-2942 Convert jdbcapi/statementJdbc30.java to
[
https://issues.apache.org/jira/browse/DERBY-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner updated DERBY-2946:
-
Affects Version/s: 10.4.0.0
> In soft upgrade mode, the metadata queries do not g
[
https://issues.apache.org/jira/browse/DERBY-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513551
]
Øystein Grøvlen commented on DERBY-2794:
I feel the introduction in the documentation is bit confusing:
"TRI
AssertionFailedError in testStalePlansOnLargeTable
--
Key: DERBY-2949
URL: https://issues.apache.org/jira/browse/DERBY-2949
Project: Derby
Issue Type: Bug
Components: Regression Test
Reoccurrence of DERBY-2842: derbynet/testconnection.java fails with
'...Connection refused: connect' expecting 'Connection refused'
---
Key: DERBY-2948
Reoccurrence of DERBY-861: Intermittent failure of store/readlocks.sql
---
Key: DERBY-2947
URL: https://issues.apache.org/jira/browse/DERBY-2947
Project: Derby
Issue Type:
[
https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513532
]
Ole Gunnar Borstad commented on DERBY-1387:
---
I want to read and write database-wide properties dynamically.
Stanley Bradbury wrote:
As stated in my comment on the TERRITORY_BASED collation problem at:
https://issues.apache.org/jira/browse/DERBY-2896#action_12513395
This problem greatly limits the use of TERRITORY_BASED collation and
for the sake of that feature needs to be fixed quickly. Rather tha
[
https://issues.apache.org/jira/browse/DERBY-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2936:
--
Derby Info: [Patch Available]
> Use java.nio.ByteBuffer for buffering in DDMWriter
> --
[
https://issues.apache.org/jira/browse/DERBY-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2936:
--
Attachment: derby-2936-2.stat
derby-2936-2.diff
Attaching a patch which
[
https://issues.apache.org/jira/browse/DERBY-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513501
]
Øystein Grøvlen commented on DERBY-2940:
Can anyone who knows the collation work tell whether this is expecte
[
https://issues.apache.org/jira/browse/DERBY-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2878:
--
Attachment: derby-2878-3a.diff
Attaching a new and simpler patch (3a) which replaces pa
[
https://issues.apache.org/jira/browse/DERBY-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513461
]
Knut Anders Hatlen commented on DERBY-2518:
---
> hm...How do I throw the SQLException from the static initial
60 matches
Mail list logo
