Derby should follow SQL standards when operand(s) in the collation operation
have collation derivation of NONE
--
Key: DERBY-2678
URL:
[
https://issues.apache.org/jira/browse/DERBY-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497731
]
Mamta A. Satoor commented on DERBY-2678:
Derby 10.3 implements the item number 2) above but item number 1)
[
https://issues.apache.org/jira/browse/DERBY-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497734
]
Mamta A. Satoor commented on DERBY-2669:
Derby is behaving as expected when JDBC url has no territory
Hi Ollie,
I think you have to use a stored procedure to get the primary key. The
call to this stored procedure would be:
call sysibm.sqlprimarykeys(catalog,schema,table,options);
Since there are no catalogs in Derby, the following stored procedure
call would provide you with the pk
Knut, I haven't been able to spend much time on your email reponse but I
just wanted to share that Derby is not doing anything special for any
character (meaning soft hyphens or other punctuation characters). We just
rely on RuleBasedCollator provided by JVM for a given locale and we let that
[
https://issues.apache.org/jira/browse/DERBY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497780
]
Bernt M. Johnsen commented on DERBY-4:
--
Bryan wrote:
It's hard to see how to interpret the START WITH and
[
https://issues.apache.org/jira/browse/DERBY-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497789
]
Knut Anders Hatlen commented on DERBY-2247:
---
Are you suggesting to signature change from public
developers guide URL attributes enumeration lacks items
---
Key: DERBY-2679
URL: https://issues.apache.org/jira/browse/DERBY-2679
Project: Derby
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/DERBY-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-2679:
-
Priority: Minor (was: Major)
developers guide URL attributes enumeration lacks items
[
https://issues.apache.org/jira/browse/DERBY-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2642:
--
Attachment: derby-2642-2.stat
derby-2642-2.diff
Attaching patch which
Bryan Pendleton [EMAIL PROTECTED] writes:
Thanks for the very clear explanation, Knut Anders!
As I can't see that the subsequent exceptions will provide any
significant value, I'm tempted to go for this solution. The code will be
a lot simpler this way, and I think it would also be clearer
I forgot to mention that machines for sles and vista are temporarily in
use for other purposes, so they will not show any results.
This also applies for all testing on the 10.2-branch.
I hope to restart this again in 1 or 2 days.
Henri
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*Daily*
[
https://issues.apache.org/jira/browse/DERBY-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497880
]
Knut Anders Hatlen commented on DERBY-2379:
---
Thanks for addressing my comments, Anurag! I will take a look
[
https://issues.apache.org/jira/browse/DERBY-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2642:
--
Derby Info: [Patch Available]
Convert lang/dynamicLikeOptimization.sql to JUnit
[
https://issues.apache.org/jira/browse/DERBY-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-2647.
---
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was:
[
https://issues.apache.org/jira/browse/DERBY-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497895
]
Daniel John Debrunner commented on DERBY-2644:
--
I'd thought that this issue might be related to the
Issue Subscription
Filter: Derby: JIRA issues with patch available (13 issues)
Subscriber: derby-dev
Key Summary
DERBY-2642 Convert lang/dynamicLikeOptimization.sql to JUnit
https://issues.apache.org/jira/browse/DERBY-2642
DERBY-2549 ArrayIndexOutOfBoundsException in
[Auto-generated mail]
*Daily* 540182/2007-05-21 18:00:14 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
0311311 074.40% derbyall
F:0,E:1380448031 0 707.31% suitesAll
sles
Reference manual section Setting attributes.. lacks upgrade=true attribute
Key: DERBY-2680
URL: https://issues.apache.org/jira/browse/DERBY-2680
Project: Derby
Hi
As part of working of Junit test conversion, I added one of the
sample junit tests to derby src which does nothing important.
I ran ant all without any errors.
The test can be run successfully as a standalone tests:
[EMAIL PROTECTED] trunk]$ java junit.textui.TestRunner
[
https://issues.apache.org/jira/browse/DERBY-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497919
]
Kathey Marsden commented on DERBY-2644:
---
Dan wrote:
I'd thought that this issue might be related to the
[
https://issues.apache.org/jira/browse/DERBY-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497920
]
Daniel John Debrunner commented on DERBY-2644:
--
The problem is caused by the upgrade test fixture
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1465:
--
The patch attached has a conflict with DERBY-2671, so needs to be redone.
Ignore the patch
On 5/22/07, Ramin Moazeni [EMAIL PROTECTED] wrote:
Hi
As part of working of Junit test conversion, I added one of the
sample junit tests to derby src which does nothing important.
I ran ant all without any errors.
The test can be run successfully as a standalone tests:
[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/DERBY-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner updated DERBY-2644:
-
Attachment: derby2644_policyreload.txt
Patch to not attempt to reload the
[
https://issues.apache.org/jira/browse/DERBY-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497942
]
Daniel John Debrunner commented on DERBY-2644:
--
Patch Committed revision 540658
multiple junit
Do we need to write release notes for wrong results bugs, or are they just
treated as normal Jira entries? See esp. issues linked to DERBY-2034.
I think DERBY-2370 needs a release note because a query that used to compile and
execute now throws an error, per:
[
https://issues.apache.org/jira/browse/DERBY-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-2599:
---
Attachment: DERBY2599_getNull_should_set_collation_info_v1_stat.txt
On 5/22/07, Army [EMAIL PROTECTED] wrote:
Do we need to write release notes for wrong results bugs, or are they just
treated as normal Jira entries? See esp. issues linked to DERBY-2034.
I think DERBY-2370 needs a release note because a query that used to compile and
execute now throws an
Hi,
I looked at the Release Notes-per version option of JIRA as well as
the trunk/RELEASE-NOTES.html generated by Rick's release notes
generator (see DERBY-2570) and I notice that many bugs are listed that
were already fixed in 10.2.2.0.
JIRA allows us to add many versions in the 'Fixed-In'
Hello,
In my work on DERBY-2646, I have stumbled upon some issues that can
greatly affect the performance of accessing Clobs, especially updating them.
Currently Clobs are stored on disk in the modified UTF-8 encoding. This
uses one to three bytes to represent a single character. Since the
These two classes have direct calls to DataValueFactory methods that
return a CHAR/VARCHAR DataValueDescriptor with UCS_BASIC collation.
CharConstantNode
Two calls to DataValueFactory.getCharDataValue(String)
ResultColumn
Two calls to DataValueFactory.getVarcharDataValue(String)
I
I will look into this 2 classes.
Mamta
On 5/22/07, Daniel John Debrunner [EMAIL PROTECTED] wrote:
These two classes have direct calls to DataValueFactory methods that
return a CHAR/VARCHAR DataValueDescriptor with UCS_BASIC collation.
CharConstantNode
Two calls to
think that should become the rule in the future too, so that only 1
released version should appear for 'fixed-in' for most bugs.
In general, I agree with you: once a bug is marked fixed in a particular
released version, it should be assumed to be fixed in all higher
released versions.
But is
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1465:
--
Attachment: DERBY-1465_stat.txt
NetworkServerControl.start() should throw an exception and
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1465:
--
Attachment: DERBY-1465_diff.txt
Patch for this issue. start() will now wait until the server
Myrna van Lunteren wrote:
Hi,
I looked at the Release Notes-per version option of JIRA as well as
the trunk/RELEASE-NOTES.html generated by Rick's release notes
generator (see DERBY-2570) and I notice that many bugs are listed that
were already fixed in 10.2.2.0.
JIRA allows us to add many
Myrna van Lunteren wrote:
I
think that should become the rule in the future too, so that only 1
released version should appear for 'fixed-in' for most bugs. (There
are a few that were backported after the latest release on an older
branch - those would still have multiple fix-versions).
I
[
https://issues.apache.org/jira/browse/DERBY-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A B updated DERBY-1816:
---
Attachment: d1816_recycleCleanup_v3.patch
Committed d1816_recycleCleanup_v3.patch with svn # 540740:
URL:
[
https://issues.apache.org/jira/browse/DERBY-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali resolved DERBY-2549.
---
Resolution: Fixed
I have committed the fix to the trunk with change 540657, and backported
[javadoc]
C:\nightlies\main\src\opensource\java\engine\org\apache\derby\impl\sql\execute\WriteCursorConstantAction.java:184:
warning - @param argument ec is not a parameter name.
[javadoc]
C:\nightlies\main\src\opensource\java\engine\org\apache\derby\catalog\TypeDescriptor.java:159:
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1465:
--
Attachment: releaseNote.html
NetworkServerControl.start() should throw an exception and not
Kathey Marsden [EMAIL PROTECTED] writes:
Myrna van Lunteren wrote:
I
think that should become the rule in the future too, so that only 1
released version should appear for 'fixed-in' for most bugs. (There
are a few that were backported after the latest release on an older
branch - those
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden reassigned DERBY-700:
Assignee: Kathey Marsden
Derby does not prevent dual boot of database from different
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1465:
--
Derby Info: [Patch Available, Existing Application Impact] (was: [Existing
Application
[
https://issues.apache.org/jira/browse/DERBY-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laura Stewart reassigned DERBY-1964:
Assignee: Laura Stewart
Update the documentation of SYSCS_UTIL.SYSCS_COMPRESS_TABLE for
[
https://issues.apache.org/jira/browse/DERBY-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A B reopened DERBY-2370:
Reopening to attach release note.
EXISTS may return the wrong value for sub-queries involving set operations
I looked at CharConstantNode. The correct collation setting happens at bind
time for this node and at the same time, we use that collation to see if we
need to switch from SQLxxx to CollatorSQLxxx. This code is in
CharConstantNode.bindExpression(). I guess this could be done at init time
where
Bryan Pendleton [EMAIL PROTECTED] writes:
Thanks for the very clear explanation, Knut Anders!
As I can't see that the subsequent exceptions will provide any
significant value, I'm tempted to go for this solution. The code will be
a lot simpler this way, and I think it would also be clearer
[
https://issues.apache.org/jira/browse/DERBY-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A B updated DERBY-2370:
---
Attachment: releaseNote.html
Attaching first draft of the release note.
EXISTS may return the wrong value for
[
https://issues.apache.org/jira/browse/DERBY-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A B resolved DERBY-2370.
Resolution: Fixed
Derby Info: [Existing Application Impact, Release Note Needed] (was:
[Existing Application
[
https://issues.apache.org/jira/browse/DERBY-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner updated DERBY-2644:
-
Component/s: Security
Was an issue in the policy reloading stored procedure.
SetQueryTimeoutTest. fails in J2ME environment
--
Key: DERBY-2681
URL: https://issues.apache.org/jira/browse/DERBY-2681
Project: Derby
Issue Type: Bug
Components: Regression Test Failure
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498037
]
Kathey Marsden commented on DERBY-700:
--
Thanks Suresh for the patch! I was wondering, why do we need
[
https://issues.apache.org/jira/browse/DERBY-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner resolved DERBY-2644.
--
Resolution: Fixed
Fix Version/s: 10.3.0.0
Tinderbox runs show no errors
Kristian Waagan [EMAIL PROTECTED] writes:
Hello,
In my work on DERBY-2646, I have stumbled upon some issues that can
greatly affect the performance of accessing Clobs, especially updating
them.
[]
To summarize my view on this...
Pros, UTF-8 : more space efficient for US-ASCII, same
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden resolved DERBY-1465.
---
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: [Existing Application
To add my 2 cents: I like using whichever tool suits my needs at a
particular point, so I wouldn't want this to be a mandatory thing, but
it would be nice to see the nightly reports that currently run the
textui.TestRunner be a bit more helpful, especially in the case of
hangs, or failures in
[
https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498050
]
Suresh Thalamati commented on DERBY-700:
[ Show » ] Kathey Marsden [22/May/07 03:22 PM] Thanks Suresh for the
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498051
]
Daniel John Debrunner commented on DERBY-1465:
--
Should the thread you create via this start method be a
Knut Anders Hatlen wrote:
Kristian Waagan [EMAIL PROTECTED] writes:
Hello,
In my work on DERBY-2646, I have stumbled upon some issues that can
greatly affect the performance of accessing Clobs, especially updating
them.
[]
To summarize my view on this...
Pros, UTF-8 : more space
Kristian Waagan wrote:
Knut Anders Hatlen wrote:
Kristian Waagan [EMAIL PROTECTED] writes:
Hello,
In my work on DERBY-2646, I have stumbled upon some issues that can
greatly affect the performance of accessing Clobs, especially updating
them.
[]
To summarize my view on this...
org.apache.derbyTesting.functionTests.tests.store.EncryptionKeyAESTest tests
fail with java.security.AccessControlException: access denied
(java.util.PropertyPermission user.dir read) on IBM 1.4.2
Kristian Waagan wrote:
Hello,
In my work on DERBY-2646, I have stumbled upon some issues that can
greatly affect the performance of accessing Clobs, especially updating
them.
Currently Clobs are stored on disk in the modified UTF-8 encoding. This
uses one to three bytes to represent a
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498057
]
Kathey Marsden commented on DERBY-1465:
---
Thanks Dan for looking.
I don't think it should be a daemon thread
Myrna van Lunteren wrote:
To add my 2 cents: I like using whichever tool suits my needs at a
particular point, so I wouldn't want this to be a mandatory thing,
+1
A verbose text based runner might be great for a human looking into a
failure, but may not be the best option for a nightly or
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498058
]
Daniel John Debrunner commented on DERBY-1465:
--
Could you also explain the lifetime of this new thread
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498061
]
Kathey Marsden commented on DERBY-1465:
---
Dan asked:
Could you also explain the lifetime of this new thread
[
https://issues.apache.org/jira/browse/DERBY-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-1491:
---
It appears to me was fixed in 10.2.2.0.
Reopening to add fix version.
Provide ALTER
[
https://issues.apache.org/jira/browse/DERBY-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1491.
-
Resolution: Fixed
Fix Version/s: (was: 10.3.0.0)
10.2.2.0
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498068
]
Daniel John Debrunner commented on DERBY-1465:
--
The old thread was started as a daemon thread, in
[
https://issues.apache.org/jira/browse/DERBY-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-1547:
---
Add svn version number to DatabaseMetaData getDatabaseProductVersion and
[
https://issues.apache.org/jira/browse/DERBY-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-1547.
---
Resolution: Fixed
Fix Version/s: (was: 10.3.0.0)
[
https://issues.apache.org/jira/browse/DERBY-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1547.
-
Add svn version number to DatabaseMetaData getDatabaseProductVersion and
[
https://issues.apache.org/jira/browse/DERBY-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-1783:
---
Logical error in code for determining mode for opening of log files
[
https://issues.apache.org/jira/browse/DERBY-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1783.
-
Resolution: Fixed
Fix Version/s: 10.2.1.6
10.2.2.0
Logical
[
https://issues.apache.org/jira/browse/DERBY-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-1491:
---
Provide ALTER TABLE functionality to change a column's default value
[
https://issues.apache.org/jira/browse/DERBY-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-1811:
---
Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp
with a
[
https://issues.apache.org/jira/browse/DERBY-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1811.
-
Resolution: Fixed
Fix Version/s: 10.2.1.6
10.2.2.0
Embedded
[
https://issues.apache.org/jira/browse/DERBY-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1491.
-
Resolution: Fixed
Fix Version/s: 10.3.0.0
Provide ALTER TABLE functionality to
[
https://issues.apache.org/jira/browse/DERBY-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-1547:
---
Add svn version number to DatabaseMetaData getDatabaseProductVersion and
[
https://issues.apache.org/jira/browse/DERBY-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1547.
-
Resolution: Fixed
Fix Version/s: 10.3.0.0
Add svn version number to
[
https://issues.apache.org/jira/browse/DERBY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1836.
-
Resolution: Fixed
Fix Version/s: 10.2.1.6
10.2.2.0
Message
[
https://issues.apache.org/jira/browse/DERBY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-1836:
---
Message XJ215 should be updated to reflect that Clob/Blob are referring to
method
[
https://issues.apache.org/jira/browse/DERBY-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren reopened DERBY-1862:
---
Simple hash improves performance
[
https://issues.apache.org/jira/browse/DERBY-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1862.
-
Resolution: Fixed
Fix Version/s: 10.2.1.6
10.2.2.0
Closing
[
https://issues.apache.org/jira/browse/DERBY-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498071
]
Myrna van Lunteren commented on DERBY-1890:
---
note: doc fix was backported to 10.2, but actual message was
[
https://issues.apache.org/jira/browse/DERBY-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-2279:
--
Fix Version/s: (was: 10.0.2.2)
10.2.2.1
JDBC3 driver is loaded
[
https://issues.apache.org/jira/browse/DERBY-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden reopened DERBY-1465:
---
There are some issues with the change noted in Dan's comments. Backing out the
change and
[
https://issues.apache.org/jira/browse/DERBY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-4:
Attachment: samples.ij
insertOrderBy_v3.diff
It turns out that I had a major
90 matches
Mail list logo
