[ http://issues.apache.org/jira/browse/DERBY-1363?page=all ]
Kathey Marsden updated DERBY-1363:
--
Fix Version/s: 10.2.0.0
Setting this to fix version 10.2 as a high value fix candidate. This issue
has hit virtually every new developer that has joined
[
http://issues.apache.org/jira/browse/DERBY-694?page=comments#action_12423780 ]
V.Narayanan commented on DERBY-694:
---
The following test cases would test the patch in greater detail
1) Generate a case which will cause a ABNUOWRM that will
Rick said for 10.2 we could use the Fix Version on unassigned issues to
mark high value fix candidates for the release and then iteratively
adjust the list as individual issues look like could not be fixed by the
fix date.
Long gone are the days where I knew every significant bug
[
http://issues.apache.org/jira/browse/DERBY-1320?page=comments#action_12423783 ]
Knut Anders Hatlen commented on DERBY-1320:
---
Hi Manjula,
Does your editor automatically strip trailing white-space when you
save a file? There are quite
[
http://issues.apache.org/jira/browse/DERBY-1543?page=comments#action_12423787 ]
Satheesh Bandaram commented on DERBY-1543:
--
Yes, I was refering to Derby's handling of synonyms for GRANT/REVOKE. It was
debated early on whether or how
[ http://issues.apache.org/jira/browse/DERBY-1546?page=all ]
Knut Anders Hatlen resolved DERBY-1546.
---
Fix Version/s: 10.2.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thank you for looking at the patch, Rick.
[
http://issues.apache.org/jira/browse/DERBY-244?page=comments#action_12423789 ]
Knut Anders Hatlen commented on DERBY-244:
--
Thanks for your comments, Myrna. The issue was that the test harness sets
console.encoding to Cp1252. I think
[ http://issues.apache.org/jira/browse/DERBY-244?page=all ]
Knut Anders Hatlen updated DERBY-244:
-
Attachment: 244-2.diff
244-2.stat
Attaching new patch (244-2.diff). The only change from the previous patch is
that it uses
Hi Mamta,
While it is OK for 'mamta2' to create the view, in your example,
attempts to GRANT access to other users on view 'v1' should raise an
error. This is because user 'mamta2' has been granted SELECT privilege
and this user is attempting to allow other users to SELECT from table
created by
On 7/26/06, Army [EMAIL PROTECTED] wrote: 1 - Some whitespace inconsistencies between new code and existing code.
Thanks for spotting that. I was using 2 different IDEs with slightly different editor settings.I'll make the corrective action on those misaligned code that are relevent to this patch.
Myrna van Lunteren wrote:
Hi,
..
Now here are my ponderables:
- why does derbynet.jar need to have this permission, isn't it
sufficient for derby.jar to have them (derby.jar has these permissions
already).
I think it should be sufficient if derby.jar has these permissions, and
that you have
[Auto-generated mail]
*Derby* 425787/2006-07-26 19:46:11 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
NA NA NANA SunOS-5.10_i86pc-i386
Details in
unable to boot exisiting database from network server when running with
security manager
Key: DERBY-1598
URL: http://issues.apache.org/jira/browse/DERBY-1598
[ http://issues.apache.org/jira/browse/DERBY-1598?page=all ]
Andreas Korneliussen closed DERBY-1598.
---
Resolution: Duplicate
Duplicate: http://issues.apache.org/jira/browse/DERBY-1241
unable to boot exisiting database from network server when
I think this is the same problem as reported in
http://issues.apache.org/jira/browse/DERBY-1241
Andreas
[
http://issues.apache.org/jira/browse/DERBY-1241?page=comments#action_12423822 ]
Andreas Korneliussen commented on DERBY-1241:
-
The following scenario reproduced this problem:
1. Start Network server with security manager enabled
[
http://issues.apache.org/jira/browse/DERBY-1545?page=comments#action_12423828 ]
Andreas Korneliussen commented on DERBY-1545:
-
Improved the original patch by also granting permission to
${derbyTesting.serverhost}.
This should make
[
http://issues.apache.org/jira/browse/DERBY-1417?page=comments#action_12423829 ]
Knut Anders Hatlen commented on DERBY-1417:
---
Hi Kristian,
I have had a look at your patch, and I have a couple of comments and
questions:
1) I
Satheesh Bandaram wrote:
Hi Mamta,
While it is OK for 'mamta2' to create the view, in your example,
attempts to GRANT access to other users on view 'v1' should raise an
error. This is because user 'mamta2' has been granted SELECT privilege
and this user is attempting to allow other users
[ http://issues.apache.org/jira/browse/DERBY-1241?page=all ]
Kathey Marsden updated DERBY-1241:
--
Summary: When booting a database under security manager, boot may
fail with message java.sql.SQLException: Java exception: 'access denied
[ http://issues.apache.org/jira/browse/DERBY-1559?page=all ]
Andreas Korneliussen updated DERBY-1559:
Attachment: DERBY-1559.diff
DERBY-1559.stat
Attached is a patch which does the following:
EXTDTAReaderInputStream: this is a
Clob.getSubString() throws NullPointerException when created by updatable
result set
Key: DERBY-1599
URL: http://issues.apache.org/jira/browse/DERBY-1599
Project:
[ http://issues.apache.org/jira/browse/DERBY-1599?page=all ]
Knut Anders Hatlen updated DERBY-1599:
--
Attachment: Repro.java
Attaching repro.
Clob.getSubString() throws NullPointerException when created by updatable
result set
[
http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12423846 ]
John H. Embretsen commented on DERBY-1564:
--
In the DerbyNet (and DerbyNetClient) framework the test harness spawns two new
JVMs when running the
[ http://issues.apache.org/jira/browse/DERBY-1554?page=all ]
Rick Hillegas updated DERBY-1554:
-
Fix Version/s: 10.2.0.0
Priority: Critical (was: Major)
Assigning this bug to 10.2 and bumping its priority to Critical. This will make
it visible
[ http://issues.apache.org/jira/browse/DERBY-803?page=all ]
Fernanda Pizzorno updated DERBY-803:
Attachment: suggestion-803.diff
suggestion-803.stat
I have managed to reproduce this failure, and I agree with Deepa's
interpretation
[
http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12423858 ]
Andreas Korneliussen commented on DERBY-1564:
-
I think experimenting with different heap-sizes is slightly off-track, since
all it may prove is that
Rick Hillegas (JIRA) wrote:
Assigning this bug to 10.2 and bumping its priority to Critical. This will make
it visible to bug-fixers. Once the Urgency field appears, we can adjust the
severity of this bug.
I think it is really important not to muck with the priority (mental
translation
After Andrew wrestles the Urgency field onto our JIRAs, we will revisit
all of the Blocker/Critical bugs which we've marked for 10.2. Currently,
there are 7 of these bugs. Of those 7, only 2 are really
Blocker/Critical severity according to the JIRA definitions below
(DERBY-1564 and
[
http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12423866 ]
Tomohito Nakayama commented on DERBY-1559:
--
In DERBY-1535, it was suggested that Engine itself takes more amount of memory
in the case ps.setBytes was
I'm been thinking about the derby.database.sqlAuthorization property
while trying to write a JUnit test that uses GRANT/REVOKE.
Do we really need such a property to be part of the public api, it just
makes Derby that little bit harder to use.
Why not base the switching of the mode on the first
Is this correct ?
I was working on modifying the upgrade test to test grant/revoke. I
had wrongly understood that for grant/revoke to work on upgraded
databases, we need to set derby.database.sqlAuthorization to true
*during* upgrade. After seeing recent discussion by Dan and Satheesh,
I think
Rick Hillegas wrote:
we will revisit all of the Blocker/Critical bugs which we've marked
for 10.2.
Yes, priorities (mental translation SEVERITIES) are quite out of whack,
not only because of the misnamed field, but because Major is the default.
After we get Urgency in and all the fields
[
http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423873 ]
Rick Hillegas commented on DERBY-1252:
--
It seems to me that SYSIBM.METADATA exists to support the JCC driver. Maybe we
could let this procedure continue to
[ http://issues.apache.org/jira/browse/DERBY-1565?page=all ]
Andrew McIntyre updated DERBY-1565:
---
Urgency: Blocker
Adjust documentation to comply with latest Apache copyright/license
requirements
[
http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423879 ]
Dag H. Wanvik commented on DERBY-1252:
--
Yes, that's what I had in mind for my alternative two above. If
people are OK with that approach I can make a patch
I've added the Urgency field in JIRA. In the edit screens, I have it
appear just underneath priority for easy editing. To filter by
Urgency, though, on the Find Issues screen you'll find the Urgency
field at the very bottom in the Custom Fields section.
Let me know if you have any issues with
On 7/26/06, Kathey Marsden [EMAIL PROTECTED] wrote:
I created a derby-dev JIRA account so we can get weekly patch list
notification. But there are few outstanding issues.
1) derby-dev needs JIRA developer access so it can subscribe to the
patch report
done.
2) [EMAIL PROTECTED] needs to
[
http://issues.apache.org/jira/browse/DERBY-1241?page=comments#action_12423884 ]
Myrna van Lunteren commented on DERBY-1241:
---
I tried my scenario (see DERBY-1598, marked as duplicate to this one) with
10.1.3.1 (build 417277) and
[
http://issues.apache.org/jira/browse/DERBY-1574?page=comments#action_12423885 ]
Manish Khettry commented on DERBY-1574:
---
To me it seems CoalesceFunctionNode should provide a preprocess method but I'm
not an authority either! While
[ http://issues.apache.org/jira/browse/DERBY-939?page=all ]
Yip Ng updated DERBY-939:
-
Attachment: derby939trunkstatpatch2.txt
derby939trunkdiffpatch2.txt
I fixed the whitespace issue. Resubmitting the patch for review. Thanks!
Satheesh Bandaram wrote:
Daniel John Debrunner wrote:
Do we really need such a property to be part of the public api, it just
makes Derby that little bit harder to use.
Why not base the switching of the mode on the first successful execution
of a GRANT statement?
I also dislike the two
JUnit test SURQueryMixTest does not follow the typical pattern for JUnit tests.
---
Key: DERBY-1600
URL: http://issues.apache.org/jira/browse/DERBY-1600
Project: Derby
Thanks, Andrew. I can see the Urgency field after I select the Edit
action. Before that, however, I can't seem to find Urgency on the bug
summary screen. I expected to see it in the upper left hand corner in
the Issue Details box, maybe undeneath or above the Priority field. But
it's not
On 7/27/06, Satheesh Bandaram [EMAIL PROTECTED] wrote:
Yes, for an extent database, you have to upgrade the database to 10.2
and then set the sqlAuthorization property as a database property to
turn on SQL authorization.
Thanks for clarifying this Satheesh. I tried this by setting it as a
On 7/27/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Thanks, Andrew. I can see the Urgency field after I select the Edit
action. Before that, however, I can't seem to find Urgency on the bug
summary screen. I expected to see it in the upper left hand corner in
the Issue Details box, maybe
Deepa Remesh wrote:
Thanks for clarifying this Satheesh. I tried this by setting it as a
database property for the upgraded database. However, grant/revoke
does not work right away. It works after I shutdown/reconnect to the
database. Is this the expected behaviour for this property? If so,
Hi
I am trying to locate DataFactory from the moniter when i call
Monitor.getMonitor().findService (DataFactory.MODULE, databasename)
It returns me an instance of org.apache.derby.impl.db.BasicDatabase
Am I doing something wrong here ? Or its expected behavior ? In that
case how to i get the
[
http://issues.apache.org/jira/browse/DERBY-1600?page=comments#action_12423905 ]
Andreas Korneliussen commented on DERBY-1600:
-
See:
http://junit.sourceforge.net/doc/cookstour/cookstour.htm
run() is a template method, it will call:
[ http://issues.apache.org/jira/browse/DERBY-1057?page=all ]
Laura Stewart updated DERBY-1057:
-
Attachment: devguide_html2.zip
I have updated the documentation for the Dev Guide for Grant/Revoke and
included the updated/new files in the
[ http://issues.apache.org/jira/browse/DERBY-1057?page=all ]
Laura Stewart updated DERBY-1057:
-
Attachment: ref_html2.zip
I have updated the Reference Manual topics for Grant/Revoke. However there are
several questions that I have which I need your
[
http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12423910 ]
Laura Stewart commented on DERBY-1057:
--
The updates to the Reference Manual are in ref_html2.zip
FYI - These updates and the updates in devguide_html2.zip
[ http://issues.apache.org/jira/browse/DERBY-1241?page=all ]
Rick Hillegas updated DERBY-1241:
-
Urgency: Urgent
Description:
logmirror.ctrl is getting accessed outside the privileged block when the
checkpoint instant is invalid on log factory
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Rick Hillegas updated DERBY-1564:
-
Urgency: Urgent
Bumping urgency.
wisconsin.sql test failed in DerbyNet framework, VM for network server got
OutOfMemoryError
[ http://issues.apache.org/jira/browse/DERBY-1554?page=all ]
Rick Hillegas updated DERBY-1554:
-
Urgency: Urgent
Bumping urgency.
IDENTITY_VAL_LOCAL() returned value is modified incorrectly by a multi-row
INSERT statement.
[ http://issues.apache.org/jira/browse/DERBY-1600?page=all ]
Daniel John Debrunner closed DERBY-1600.
Resolution: Invalid
My confusion, Sorry, just getting used to Junit tests
JUnit test SURQueryMixTest does not follow the typical pattern for
[ http://issues.apache.org/jira/browse/DERBY-1554?page=all ]
Rick Hillegas updated DERBY-1554:
-
Priority: Major (was: Critical)
IDENTITY_VAL_LOCAL() returned value is modified incorrectly by a multi-row
INSERT statement.
[ http://issues.apache.org/jira/browse/DERBY-1405?page=all ]
Rick Hillegas updated DERBY-1405:
-
Urgency: Urgent
Priority: Major (was: Critical)
Adjusting urgency and severity.
New javadoc needs to be wired into documentation
[
http://issues.apache.org/jira/browse/DERBY-803?page=comments#action_12423919 ]
Deepa Remesh commented on DERBY-803:
Thanks Fernanda for picking this up.
I am wondering if this solution will fix all cases. I think this solution is in
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Rick Hillegas updated DERBY-1564:
-
Priority: Major (was: Critical)
wisconsin.sql test failed in DerbyNet framework, VM for network server got
OutOfMemoryError
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
Rick Hillegas updated DERBY-700:
Urgency: Urgent
Bumping urgency.
Derby does not prevent dual boot of database from different classloaders on
Linux
[ http://issues.apache.org/jira/browse/DERBY-1537?page=all ]
Rick Hillegas updated DERBY-1537:
-
Urgency: Urgent
Bumping urgency.
Boot-time exception when running Derby tests with derbytools.jar in front of
derby.jar in the classpath.
[ http://issues.apache.org/jira/browse/DERBY-1565?page=all ]
Rick Hillegas updated DERBY-1565:
-
Priority: Major (was: Blocker)
Adjust documentation to comply with latest Apache copyright/license
requirements
[ http://issues.apache.org/jira/browse/DERBY-1377?page=all ]
Rick Hillegas updated DERBY-1377:
-
Urgency: Blocker
Priority: Major (was: Blocker)
Adjusting urgency and severity.
Update copyright headers to comply with new ASF policy
Rick Hillegas (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ]
Rick Hillegas updated DERBY-1564:
-
Priority: Major (was: Critical)
Since this test runs out of memory, does it not qualify as:
Critical
Crashes, loss of
[
http://issues.apache.org/jira/browse/DERBY-1600?page=comments#action_12423924 ]
Daniel John Debrunner commented on DERBY-1600:
--
My confusion, Sorry, just getting used to Junit tests. Thanks for the quick
feedback, helped my
Thanks, Andrew. Now I have another request: I'm trying to set up a
filter which selects issues whose Urgency is either Blocker or Urgent.
The Urgency dropdown lets me pick one but not both--unlike other
dropdowns where by pressing the control key I can select multiple items.
Can this be
I don't have strong religion about this. It's not clear whether this
problem is an artifact of the testing environment or is a serious Derby
bug. I have marked the issue as Urgent, which means that for 10.2 we
intend to investigate this issue and fix the underlying bug if there
turns out to be
Rick Hillegas wrote:
I don't have strong religion about this. It's not clear whether this
problem is an artifact of the testing environment or is a serious
Derby bug. I have marked the issue as Urgent, which means that for
10.2 we intend to investigate this issue and fix the underlying bug if
Hi Andrew,
And another question: In setting up this filter, I would also like the
results to show the Urgency field, so that I can sort on it. This also
exceeds my reach.
Thanks,
-Rick
Rick Hillegas wrote:
Thanks, Andrew. Now I have another request: I'm trying to set up a
filter which
[
http://issues.apache.org/jira/browse/DERBY-939?page=comments#action_12423927 ]
A B commented on DERBY-939:
---
No further review comments from me. +1 to commit derby939trunkdiffpatch2.txt .
Thanks Yip!
NullPointerException at ResultSet.close()
[
http://issues.apache.org/jira/browse/DERBY-1594?page=comments#action_12423928 ]
Rick Hillegas commented on DERBY-1594:
--
Committed derby-1594_v01.diff at subversion revision 426249.
List other 10.2 features which will not be available
[ http://issues.apache.org/jira/browse/DERBY-1594?page=all ]
Rick Hillegas closed DERBY-1594.
Resolution: Fixed
List other 10.2 features which will not be available after soft upgrade.
[ http://issues.apache.org/jira/browse/DERBY-1583?page=all ]
Rick Hillegas updated DERBY-1583:
-
Urgency: Normal
Assigning normal priority.
With grant revoke enabled, defining a trigger whose actions updates a table
(from different schema) results in
[ http://issues.apache.org/jira/browse/DERBY-1579?page=all ]
Rick Hillegas updated DERBY-1579:
-
Urgency: Normal
Remove SYS.SYSREQUIREDPERM from Derby 10.2. This was added for Grant Revoke
functionality
[ http://issues.apache.org/jira/browse/DERBY-1569?page=all ]
Rick Hillegas updated DERBY-1569:
-
Urgency: Normal
analyze 10.1 tests with 10.2 derby to determine which Jira fixes in 10.2 may
have existing application impact
[ http://issues.apache.org/jira/browse/DERBY-1568?page=all ]
Rick Hillegas updated DERBY-1568:
-
Urgency: Normal
run derbyall with low memory configuration for 10.2
---
Key: DERBY-1568
[ http://issues.apache.org/jira/browse/DERBY-1566?page=all ]
Rick Hillegas updated DERBY-1566:
-
Urgency: Normal
Document SQLStates in 10.2
--
Key: DERBY-1566
URL:
[ http://issues.apache.org/jira/browse/DERBY-1550?page=all ]
Rick Hillegas updated DERBY-1550:
-
Urgency: Low
procedureInTrigger has diff under jdk1.6
Key: DERBY-1550
URL:
[ http://issues.apache.org/jira/browse/DERBY-1544?page=all ]
Rick Hillegas updated DERBY-1544:
-
Urgency: Normal
Address remaining upgrade task(s) to complete full upgrade mechanism for
GRANT/REVOKE, specifically with changing database owner name from
[ http://issues.apache.org/jira/browse/DERBY-1539?page=all ]
Rick Hillegas updated DERBY-1539:
-
Urgency: Urgent
As per the functional spec attached to DERBY-1330, a trigger should be
dropped when a privilege required by the trigger is revoked.
[ http://issues.apache.org/jira/browse/DERBY-1530?page=all ]
Rick Hillegas updated DERBY-1530:
-
Urgency: Normal
DatabaseMetaData.getFunctionParameters() changing name to getFunctionColumns()
[ http://issues.apache.org/jira/browse/DERBY-1539?page=all ]
Rick Hillegas updated DERBY-1539:
-
Urgency: Normal (was: Urgent)
As per the functional spec attached to DERBY-1330, a trigger should be
dropped when a privilege required by the trigger is
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Rick Hillegas updated DERBY-1522:
-
Urgency: Normal
Switch(if supported) from Derby Authorization to Derby SQL Standard
Authorization needs to be tested
[ http://issues.apache.org/jira/browse/DERBY-1521?page=all ]
Rick Hillegas updated DERBY-1521:
-
Urgency: Normal
Upgrade test needs to be enhanced to test grant revoke
--
Key:
[ http://issues.apache.org/jira/browse/DERBY-1517?page=all ]
Rick Hillegas updated DERBY-1517:
-
Urgency: Normal
Derby Network Client to handle list of SECMEC(s) returned by
existing/released DRDA Derby Network Servers
[ http://issues.apache.org/jira/browse/DERBY-1489?page=all ]
Rick Hillegas updated DERBY-1489:
-
Urgency: Normal
Provide ALTER TABLE DROP COLUMN functionality
-
Key: DERBY-1489
[ http://issues.apache.org/jira/browse/DERBY-1458?page=all ]
Rick Hillegas updated DERBY-1458:
-
Urgency: Normal
Add MessageBundleTest to build script to verify that there are no orphaned
message ids
[ http://issues.apache.org/jira/browse/DERBY-1434?page=all ]
Rick Hillegas updated DERBY-1434:
-
Urgency: Normal
Client can send incorrect database name to server after having made multiple
connections to different databases.
[ http://issues.apache.org/jira/browse/DERBY-1430?page=all ]
Rick Hillegas updated DERBY-1430:
-
Urgency: Normal
Test parameterMapping.java often fails with DerbyNetClient on Solarisx86
[ http://issues.apache.org/jira/browse/DERBY-1433?page=all ]
Rick Hillegas updated DERBY-1433:
-
Urgency: Normal
Client driver does not handle string literals containing where current of
correctly
[ http://issues.apache.org/jira/browse/DERBY-1424?page=all ]
Rick Hillegas updated DERBY-1424:
-
Urgency: Normal
Build derbyclient.jar from a dependency list generated by classlister
-
[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ]
Rick Hillegas updated DERBY-1417:
-
Urgency: Normal
Add new, lengthless overloads to the streaming api
--
Key: DERBY-1417
[ http://issues.apache.org/jira/browse/DERBY-1397?page=all ]
Rick Hillegas updated DERBY-1397:
-
Urgency: Low
Tuning Guide: Puzzling optimizer documentation
--
Key: DERBY-1397
[ http://issues.apache.org/jira/browse/DERBY-1241?page=all ]
Suresh Thalamati reassigned DERBY-1241:
---
Assignee: (was: Suresh Thalamati)
fix might be simple one line chage of calling file.exists on mirror control
file in the privileged
[ http://issues.apache.org/jira/browse/DERBY-1373?page=all ]
Rick Hillegas updated DERBY-1373:
-
Urgency: Normal
Encrypted databases cannot be booted using the jar subprotocol (and possibly
also using http/https/classpath)
[ http://issues.apache.org/jira/browse/DERBY-1368?page=all ]
Rick Hillegas updated DERBY-1368:
-
Urgency: Normal
EOFException when reading from blob's binary stream
---
Key: DERBY-1368
[ http://issues.apache.org/jira/browse/DERBY-1363?page=all ]
Rick Hillegas updated DERBY-1363:
-
Urgency: Normal
Derby should publish a well defined coding convention per the db project
guidlines
[ http://issues.apache.org/jira/browse/DERBY-1344?page=all ]
Rick Hillegas updated DERBY-1344:
-
Urgency: Low
Placeholder for work for 10.2 snapshots
---
Key: DERBY-1344
URL:
[ http://issues.apache.org/jira/browse/DERBY-1341?page=all ]
Rick Hillegas updated DERBY-1341:
-
Urgency: Normal
LOB setBytes method(s) are currently no supported, but part of the Java 1.4
JDBC interface
1 - 100 of 140 matches
Mail list logo
