i18n Tests fail on zOS
---
Key: DERBY-1915
URL: http://issues.apache.org/jira/browse/DERBY-1915
Project: Derby
Issue Type: Test
Components: Test
Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.0.0
Envir
test lang/wisconsin gives garbage output on zOS.
Key: DERBY-1914
URL: http://issues.apache.org/jira/browse/DERBY-1914
Project: Derby
Issue Type: Test
Affects Versions: 10.2.1.6, 10.2.2.0,
Thanks Andrew. I updated the
http://wiki.apache.org/db-derby/ReferenceManualTenTwo
wiki page to reflect that this change needs to be made in the docs still.
Susan
- Original Message
From: Andrew McIntyre <[EMAIL PROTECTED]>
To: derby-dev@db.apache.org
Sent: Monday, October 2, 2006 12:1
Andrew McIntyre wrote:
> On 10/2/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote:
>
>> The docs at http://db.apache.org/derby/docs/10.2/ have a Sep 8 date.
>>
>> Unless anyone can think of a reason I should not refresh them with the
>> docs in the 10.2.1.6 candidate I'll go ahead and do so tomorrow
On 10/2/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote:
The docs at http://db.apache.org/derby/docs/10.2/ have a Sep 8 date.
Unless anyone can think of a reason I should not refresh them with the
docs in the 10.2.1.6 candidate I'll go ahead and do so tomorrow.
I have a script that pulls the do
[ http://issues.apache.org/jira/browse/DERBY-1894?page=all ]
Mike Matrigali updated DERBY-1894:
--
Fix Version/s: 10.1.3.2
merged from trunk to 10.1 branch:
m101_142:12>svn commit
Sendingjava\engine\org\apache\derby\impl\sql\compile\FromBaseTable
The docs at http://db.apache.org/derby/docs/10.2/ have a Sep 8 date.
Unless anyone can think of a reason I should not refresh them with the
docs in the 10.2.1.6 candidate I'll go ahead and do so tomorrow.
-jean
[ http://issues.apache.org/jira/browse/DERBY-1894?page=all ]
Mike Matrigali updated DERBY-1894:
--
Fix Version/s: 10.3.0.0
committed to trunk:
m3_ibm142:172>svn commit
Sendingjava\engine\org\apache\derby\impl\sql\compile\FromBaseTable.java
Sendi
Rick Hillegas wrote:
...
> Given this limited delta from the previous candidate, I would like to
> call a quick vote on 10.2.1.6 and close the polls at 5:00 pm San
> Francisco time, this Thursday, October 5. Please let me know if you need
> more time to test the new candidate.
The 10.2.1.6 distro
On 10/2/06, Daniel J Debrunner <[EMAIL PROTECTED]> wrote:
--- Laura Stewart <[EMAIL PROTECTED]> wrote:
> Hi -
>
> From the 10.2 Doc Review, I have this question about
> the SECOND function
>
http://db.apache.org/derby/docs/10.2/ref/rrefsecondfunc.html
>
> The text:
> 'If the argument is a time
--- Laura Stewart <[EMAIL PROTECTED]> wrote:
> Hi -
>
> From the 10.2 Doc Review, I have this question about
> the SECOND function
>
http://db.apache.org/derby/docs/10.2/ref/rrefsecondfunc.html
>
> The text:
> 'If the argument is a time duration or timestamp
> duration: The result
> is the sec
[
http://issues.apache.org/jira/browse/DERBY-630?page=comments#action_12439330 ]
Yip Ng commented on DERBY-630:
--
I think to properly address this issue, the current implementation for CREATE
TRIGGER needs
to handle null compilation schema. A comp
On 10/2/06, A B (JIRA) wrote:
derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with ibm131, hangs with
jdk131
-
Key: DERBY-1912
URL: http://issues.apache.org/jira/browse/DERBY-1912
Hi -
From the 10.2 Doc Review, I have this question about the SECOND function
http://db.apache.org/derby/docs/10.2/ref/rrefsecondfunc.html
The text:
'If the argument is a time duration or timestamp duration: The result
is the seconds part of the value, which is an integer between -99 and
99. A
[
http://issues.apache.org/jira/browse/DERBY-1905?page=comments#action_12439323 ]
A B commented on DERBY-1905:
> Can the code detect, at execution time, how accurate its estimate was?
Good question. I ran the query attached to this issue using the
On 10/2/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote:
Andrew McIntyre wrote:
...
> I'm very much in agreement with keeping broken links to a minimum. I
> had done a good job of eliminating most of the broken links on the
> website, but I see from Vadim's stats that the number of broken links
>
[
http://issues.apache.org/jira/browse/DERBY-1849?page=comments#action_12439320 ]
Deepa Remesh commented on DERBY-1849:
-
Myrna said "create Trigger fails with foundation because something in the Derby
source code accessed in this statement f
On 10/2/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
I have posted a new release candidate, 10.2.1.6, which addresses the
structural problems with the previous candidate. Special thanks to
Andrew for helping sand this one down. You may find 10.2.1.6 at:
http://people.apache.org/~rhillegas/10.2.1
[
http://issues.apache.org/jira/browse/DERBY-1894?page=comments#action_12439314 ]
Mamta A. Satoor commented on DERBY-1894:
Thanks, Yip. I have no more questions on the patch and I give it a +1.
> SQLSTATE 42X10 occurs when qualifying a c
On 10/1/06, James Synge <[EMAIL PROTECTED]> wrote:
but I don't understand the generated code, especially given that it's expressedas bytecode. Can someone suggest a means of debugging the executionphase (or getting a human readable form of the code)?
One way is to dump the actual generated code in
James Synge wrote:
Yes, though I've been finding it hard to understand the manner in which the
the query plan is transformed by the optimizer. For example, how
an index scan gets inserted above (?) a base table,
The query plan that you see is generated as part of the "modifyAccessPaths"
pha
[
http://issues.apache.org/jira/browse/DERBY-1849?page=comments#action_12439311 ]
Myrna van Lunteren commented on DERBY-1849:
---
I'm not sure I was clear in my previous comment.
I think currently there are 2 problems with these tests:
-
[
http://issues.apache.org/jira/browse/DERBY-1894?page=comments#action_12439306 ]
Yip Ng commented on DERBY-1894:
---
Good question, Mamta. This is actually not related to synonym. If you do
issue the query not using synonym below, it will also fai
From: Bryan Pendleton <[EMAIL PROTECTED]>
> I'd like to fix DERBY-47 and DERBY-713 (essentially the same bug), and
> so have been working to understand what is going wrong.
Great! Welcome to the community!
Thanks.
> as bytecode. Can someone suggest a means of debugging the execution
> phase
[
http://issues.apache.org/jira/browse/DERBY-1894?page=comments#action_12439294 ]
Mamta A. Satoor commented on DERBY-1894:
Yip, I have a feeling that I missing something obvious here but why should
following statement (towards the end of
storetests/st_reclaim_longcol.java fails intermittently
---
Key: DERBY-1913
URL: http://issues.apache.org/jira/browse/DERBY-1913
Project: Derby
Issue Type: Bug
Components: Regress
[ http://issues.apache.org/jira/browse/DERBY-1875?page=all ]
Laura Stewart updated DERBY-1875:
-
Attachment: derby1875_1.diff
ctuntransform36623.html
Updated the ctuntransform36623 file per the comments
from the 10.2 Doc Review.
> Doc R
derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with ibm131, hangs with
jdk131
-
Key: DERBY-1912
URL: http://issues.apache.org/jira/browse/DERBY-1912
Project: Derby
--- Rick Hillegas <[EMAIL PROTECTED]> wrote:
> While 10.2.1.6 cooks, I'd like to start a discussion
> about the follow-on
> release which will expose our JDBC4 drivers after
> Java SE 6 goes GA.
Errmmm, 10.2.1.6 does expose Derby's JDBC 4 drivers.
The primary release of an open source project
Hi -
In the 10.2 Doc Review of the Tuning Guide
http://wiki.apache.org/db-derby/TuningTenTwo
there is this comment:
In the file
http://db.apache.org/derby/docs/dev/tuning/rtuntransform472.html
there is a mention of rewriting queries:
"Users can work around this possibility by writing the query
Andrew McIntyre wrote:
...
> I'm very much in agreement with keeping broken links to a minimum. I
> had done a good job of eliminating most of the broken links on the
> website, but I see from Vadim's stats that the number of broken links
> have shot back up:
>
> http://people.apache.org/~vgritsen
[ http://issues.apache.org/jira/browse/DERBY-1894?page=all ]
Yip Ng updated DERBY-1894:
--
Attachment: derby1894-trunk-stat02.txt
derby1894-trunk-diff02.txt
Thanks for reviewing the patch, Mamta. I added a couple more testcases this
week and als
[ http://issues.apache.org/jira/browse/DERBY-1898?page=all ]
Suresh Thalamati resolved DERBY-1898.
-
Resolution: Invalid
Derby is not expected to work correctly, if two versions of derby jar files
are present in the classpath.
> can not boot de
[ http://issues.apache.org/jira/browse/DERBY-1873?page=all ]
Laura Stewart closed DERBY-1873.
Resolution: Fixed
Derby Info: (was: [Patch Available])
Closing this issue. All of the comments in the 10.2 Doc Review wiki have
been addressed.
http://wi
[
http://issues.apache.org/jira/browse/DERBY-1894?page=comments#action_12439244 ]
Mamta A. Satoor commented on DERBY-1894:
Yip, I reviewed the code and it looks good to me. For the tests, should we have
a test case where a correlation na
While 10.2.1.6 cooks, I'd like to start a discussion about the follow-on
release which will expose our JDBC4 drivers after Java SE 6 goes GA. In
the interests of quickly vetting the follow-on release, I propose that
we spin it as a bugfix release cut from the living, growing end of the
10.2 bra
Good idea, Bryan. Perhaps dumping it in XML as a format is one option to start with. (I think this sort of facility can be applied to a more general case of dump outputs.) Then a explain tool can be used or implemented to read the XML data and produce something more visually readable. Of course
Rick Hillegas wrote:
Hi Bryan,
A modest first step might be to output the plans in xml. The ouptut
could then be post-processed into the format needed by your favorite
graph visualization tool. Even just pulling the xml into your browser
might be more readable than what we have today.
Agre
[ http://issues.apache.org/jira/browse/DERBY-1678?page=all ]
Rick Hillegas updated DERBY-1678:
-
Attachment: derby-1678-10.2_bumpVersionNumbers_09.diff
Commit derby-1678-10.2_bumpVersionNumbers_09.diff at subversion revision
452134. This bumps the last
Bryan Pendleton wrote:
One place I struggle is that I find logged query plans to be rather
intimidating and hard to read. I've been thinking that it might be
useful to put some effort into either improving the output of the query
plan dumper, or perhaps coming up with some other tools for display
Hi Bryan,
A modest first step might be to output the plans in xml. The ouptut
could then be post-processed into the format needed by your favorite
graph visualization tool. Even just pulling the xml into your browser
might be more readable than what we have today.
Regards,
-Rick
Bryan Pendl
Dag H. Wanvik wrote:
insert into greetings(ch) values ('bonjour');
ij> insert into greetings values ('bonjour');
These two don't look identical. The second one is missing (ch).
thanks,
bryan
Hi,
The 10.2 reference manual states
(http://db.apache.org/derby/docs/10.2/ref/rrefsqlj37836.html):
> GENERATED ALWAYS
>
> An identity column that is GENERATED ALWAYS will increment the
> default value on every insertion and will store the incremented
> value into the column. Unlike
[
http://issues.apache.org/jira/browse/DERBY-1904?page=comments#action_12439221 ]
A B commented on DERBY-1904:
Posting email reply from Dag Wanvik (derby-dev) in case Cédric isn't subscribed
to that list:
>> ij version 10.1
>> ij> connect 'jdbc:d
good time to start some discussion around the various issues in the
current Derby optimizer
One place I struggle is that I find logged query plans to be rather
intimidating and hard to read. I've been thinking that it might be
useful to put some effort into either improving the output of the que
[
http://issues.apache.org/jira/browse/DERBY-1905?page=comments#action_12439215 ]
Bryan Pendleton commented on DERBY-1905:
Can the code detect, at execution time, how accurate its estimate was?
If so, it strikes me that it would be inter
I have posted a new release candidate, 10.2.1.6, which addresses the
structural problems with the previous candidate. Special thanks to
Andrew for helping sand this one down. You may find 10.2.1.6 at:
http://people.apache.org/~rhillegas/10.2.1.6/
In addition to the structural problems, this ca
I'd like to fix DERBY-47 and DERBY-713 (essentially the same bug), and
so have been working to understand what is going wrong.
Great! Welcome to the community!
as bytecode. Can someone suggest a means of debugging the execution
phase (or getting a human readable form of the code)?
I don't k
Because of the structural problems with the first release candidate, I
am cancelling the vote on 10.2.1.5. I will post a new candidate and call
a new vote shortly.
Regards,
-Rick
Rick Hillegas wrote:
I have abandoned my first, flawed build of the 10.2 release. Thanks to
Dan, Jean, Andrew, an
[ http://issues.apache.org/jira/browse/DERBY-1866?page=all ]
Andrew McIntyre resolved DERBY-1866.
Resolution: Fixed
Derby Info: [Regression] (was: [Patch Available, Regression])
> Assert failure in sane mode for queries that used to work in 10.1
[Auto-generated mail]
** 451762/2006-10-01 18:00:07 MEST
**
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
0687687 0 106.00% lin
NA NA NANA sol
0687687 096
Issue Subscription
Filter: Derby: JIRA issues with patch available (12 issues)
Subscriber: derby-dev
Key Summary
DERBY-1866 Assert failure in sane mode for queries that used to work in
10.1.2.1
http://issues.apache.org/jira/browse/DERBY-1866
DERBY-1873 Doc Review Comments -
[ http://issues.apache.org/jira/browse/DERBY-1866?page=all ]
Mike Matrigali updated DERBY-1866:
--
Fix Version/s: 10.1.4.0
10.3.0.0
I backported this fix to both the 10.2 and 10.1 branches.
> Assert failure in sane mode for queries tha
[ http://issues.apache.org/jira/browse/DERBY-1860?page=all ]
Rick Hillegas updated DERBY-1860:
-
Attachment: derby-1860-v14.diff
Commit derby-1860-v14.diff at subversion revision 452058. This lists some
additional bugfixes which made it into the 10.2 bra
[
http://issues.apache.org/jira/browse/DERBY-1910?page=comments#action_12439177 ]
John H. Embretsen commented on DERBY-1910:
--
There seems to be a slight difference in memory usage between Windows/Linux and
Solaris platforms, which is mo
[ http://issues.apache.org/jira/browse/DERBY-1866?page=all ]
Rick Hillegas updated DERBY-1866:
-
Fix Version/s: 10.2.1.5
(was: 10.2.2.0)
(was: 10.3.0.0)
Looks like this one made it into 10.2.1.
> Assert failu
Hi,
"Cédric Gérard (JIRA)" writes:
> ij version 10.1
> ij> connect 'jdbc:derby://localhost:1528/watDB_v2';
> ij> SELECT ID_ITM, ITM_CODE FROM ITEMS WHERE ITM_CODE = COALESCE(NULL,
> ITM_CODE);
> ERROR 42X01: Syntax error: Encountered "NULL" at line 1, column 62.
The "NULL" literal here is no
[ http://issues.apache.org/jira/browse/DERBY-1610?page=all ]
Tomohito Nakayama updated DERBY-1610:
-
Attachment: DERBY-1610_7.patch
parameterMapping.out.7.diff
I upload the patch for DERBY-1610_7.patch
* Description of the patch
A B (JIRA) wrote:
Interesting observation about the disk cache--thanks for bringing that up. Is
it feasible to turn disk cache on for one of the machines that's failing and
run the tests for a couple of days to see if that makes a difference? Thanks
Øystein...
I can turn the disk cache o
[ http://issues.apache.org/jira/browse/DERBY-1902?page=all ]
Øystein Grøvlen updated DERBY-1902:
---
Attachment: derbylang.zip
derbylang.zip contains all files from one failing run of
lang/predicatePushdown.sql.
> Intermittent failures in predicatePushd
[
http://issues.apache.org/jira/browse/DERBY-1902?page=comments#action_12439136 ]
Øystein Grøvlen commented on DERBY-1902:
The failure was first observed in the nightly run on svn revision 449444. It
was not observed on 448277. However
[ http://issues.apache.org/jira/browse/DERBY-1904?page=all ]
Cédric Gérard updated DERBY-1904:
-
Attachment: stackfromderby.log
dblook.log
Hi,
Here are the asked files attached to these thread.
ITM_NAME was removed from my previous post
[ http://issues.apache.org/jira/browse/DERBY-1874?page=all ]
Ole Solberg closed DERBY-1874.
--
OK since http://www.multinet.no/~solberg/public/Apache/LargeData/Limited/testSummary-450936.html";>450936
http://www.multinet.no/~solberg/public/Apache/LargeData/Limite
[ http://issues.apache.org/jira/browse/DERBY-1910?page=all ]
Fernanda Pizzorno reassigned DERBY-1910:
Assignee: Fernanda Pizzorno
> OutOfMemoryError happens when jdbcapi/_Suite.junit was executed as
> DerbyNetClient (in jvm1.4.2)
> -
On 9/2/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote:
Bryan Pendleton wrote:
>
> Interestingly, in the generated Javadoc section of the web site, the
> corresponding
> link displays just fine:
>
http://db.apache.org/derby/javadoc/engine/org/apache/derby/iapi/types/package-summary.html#package_d
On 9/1/06, Susan Cline <[EMAIL PROTECTED]> wrote:
In the Reference manual,
http://db.apache.org/derby/docs/10.2/ref/rrefnumericlimits.html,
the 'Largest decimal precision' value is listed as 31,255.
Shouldn't this be 31? Or is there some meaning to the 255 after the 31 that I
don't understand
66 matches
Mail list logo
