[
http://issues.apache.org/jira/browse/DERBY-1738?page=comments#action_12429488 ]
Satheesh Bandaram commented on DERBY-1738:
--
This is a duplicate of the issue Rajesh has already filed. I think that is
DERBY-1686.
An user is able
[
http://issues.apache.org/jira/browse/DERBY-1651?page=comments#action_12429249 ]
Satheesh Bandaram commented on DERBY-1651:
--
Some general comments:
1) I think a design document to explain what each class does and how they
interact
: http://issues.apache.org/jira/browse/DERBY-1733
Project: Derby
Issue Type: Improvement
Affects Versions: 10.1.3.1, 10.1.3.0, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0
Environment: All platforms
Reporter: Satheesh Bandaram
Separating this issue from DERBY
[ http://issues.apache.org/jira/browse/DERBY-634?page=all ]
Satheesh Bandaram resolved DERBY-634.
-
Fix Version/s: 10.3.0.0
(was: 10.2.1.0)
Resolution: Fixed
I would like this fix backported to 10.2 release as soon
[ http://issues.apache.org/jira/browse/DERBY-634?page=all ]
Satheesh Bandaram closed DERBY-634.
---
Assignee: Satheesh Bandaram
I am closing this issue as I am not doing any further work. But I would
appreciate if someone can port this fix to 10.2 beta
[ http://issues.apache.org/jira/browse/DERBY-1538?page=all ]
Satheesh Bandaram resolved DERBY-1538.
--
Fix Version/s: 10.3.0.0
Resolution: Fixed
If anyone has itch or interest to port this to 10.2, I will leave it up to them.
This fix raises
[ http://issues.apache.org/jira/browse/DERBY-1538?page=all ]
Satheesh Bandaram closed DERBY-1538.
Closing this issue... If this fix is ported to 10.2, reopen to mark as fixed
in 10.2.
Unexpected behavior on self privilege revocation
[
http://issues.apache.org/jira/browse/DERBY-1723?page=comments#action_12429153 ]
Satheesh Bandaram commented on DERBY-1723:
--
No one can revoke a privilege from object owner, including the owner herself or
even the database owner
[
http://issues.apache.org/jira/browse/DERBY-1729?page=comments#action_12429169 ]
Satheesh Bandaram commented on DERBY-1729:
--
Hmm... I have to think about this some more, but not sure why the trigger
should fail.
Invoking Java
[
http://issues.apache.org/jira/browse/DERBY-1729?page=comments#action_12429173 ]
Satheesh Bandaram commented on DERBY-1729:
--
Hmm... Correct. It should fail. Guess just invoking the procedure itself
(outside a trigger) should fail. I
:
:(
Good luck in your next role! Hope to see you around.
David
Satheesh Bandaram wrote:
As some of you may have noticed, I have not been as active, on Apache
Derby project. My work assignment has changed and my new role does not
leave much time to continue working on Apache Derby. I
As some of you may have noticed, I have not been as active, on Apache
Derby project. My work assignment has changed and my new role does not
leave much time to continue working on Apache Derby. I was one of the
original 5 committers of Derby as the project started and stayed very
active till now.
[
http://issues.apache.org/jira/browse/DERBY-634?page=comments#action_12428436 ]
Satheesh Bandaram commented on DERBY-634:
-
Kathey, here are some answers...
1) No... There was a specific bug in the original optimization that could cause
[
http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12428170 ]
Satheesh Bandaram commented on DERBY-1057:
--
I think GRANT/REVOKE documentation to reference guide and developer guide can
be committed, following several
I committed this patch over the weekend on trunk. I would like this fix
to be ported to 10.2 Beta as soon as possible,
as I have a customer who is waiting for it. Anyone know how to get this
ported to 10.2 Beta?
Satheesh
Satheesh Bandaram (JIRA) wrote:
[
http://issues.apache.org/jira
[
http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12427580 ]
Satheesh Bandaram commented on DERBY-1057:
--
I am loooking at dev Guide. Here are some of the comments:
Notes on user authorization
Authorization
[
http://issues.apache.org/jira/browse/DERBY-634?page=comments#action_12427670 ]
Satheesh Bandaram commented on DERBY-634:
-
I propose twhere Table2.x=Table3.x and y 100)
o address this issue in phases. Here is my current thinking
Daniel John Debrunner wrote:
Deepa Remesh (JIRA) wrote:
It is not very clear to me from the spec how the following case should be
handled
- revoking permissions from dba (user who is the owner of the database).
dba has implicit permissions on all objects and we cannot revoke privileges
[
http://issues.apache.org/jira/browse/DERBY-1646?page=comments#action_12425935 ]
Satheesh Bandaram commented on DERBY-1646:
--
I think we need to document Derby Authorization mode and SQL standard
authorization mode in Derby. That is we
[ http://issues.apache.org/jira/browse/DERBY-1651?page=all ]
Satheesh Bandaram updated DERBY-1651:
-
Summary: Develop a mechanism to migrate mySQL databases to Derby.
Migration tool should include both schema and data migration options
[
http://issues.apache.org/jira/browse/DERBY-1646?page=comments#action_12425983 ]
Satheesh Bandaram commented on DERBY-1646:
--
Thanks Dan... I missed correcting that from Laura's original description. It
was little too burried down
Hi Rick,
Currently both Andrew and myself have JIRA-admin access, though Andrew
has been doing all the work lately.
I have been thinking of giving up my JIRA-admin access... May be the
right time now to switch it over to you, since you are the release
manager for 10.2.
Satheesh
Rick Hillegas
Andrew McIntyre wrote:
On 8/3/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Yes, please! If I knew the JIRA magic to do this, I would mumble it.
Could someone teach me the magic, and if necessary, give me karma to
mumble?
granted. the admin pages are your friends.
Can you please take me off
[
http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12425338 ]
Satheesh Bandaram commented on DERBY-1522:
--
1) Mamta says: after the upgrade, all the existing schemas and objects in them
should be owned by the dba
[ http://issues.apache.org/jira/browse/DERBY-1608?page=all ]
Satheesh Bandaram resolved DERBY-1608.
--
Resolution: Fixed
Submitted a fix to trunk and also added test cases.
Execution of builtin functions by a user who is not the owner of system
[
http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12424974 ]
Satheesh Bandaram commented on DERBY-1057:
--
All the answers provided by Mamta earlier are correct. Grant/Revoke statements
can only operate on one object
: DERBY-1543
URL: http://issues.apache.org/jira/browse/DERBY-1543
Project: Derby
Issue Type: Sub-task
Components: SQL
Affects Versions: 10.2.0.0
Reporter: Satheesh Bandaram
Assigned To: Satheesh Bandaram
Fix For: 10.2.0.0
[ http://issues.apache.org/jira/browse/DERBY-1543?page=all ]
Satheesh Bandaram resolved DERBY-1543.
--
Resolution: Fixed
Submitted a fix.
Address two remaining issues with GRANT/REVOKE functionality: 1) Add warning
when sqlAuthorization
[ http://issues.apache.org/jira/browse/DERBY-1543?page=all ]
Satheesh Bandaram closed DERBY-1543.
Added tests and it seems to work as expected.
Address two remaining issues with GRANT/REVOKE functionality: 1) Add warning
when sqlAuthorization
[ http://issues.apache.org/jira/browse/DERBY-1367?page=all ]
Satheesh Bandaram resolved DERBY-1367.
--
Fix Version/s: 10.2.0.0
Resolution: Fixed
Enabled grantRevoke.java test in DerbyNetClient framework.
add lang/grantrevoke.java
[
http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12424694 ]
Satheesh Bandaram commented on DERBY-1522:
--
I was looking through all GRANT/REVOKE sub-tasks and related bugs. I am not
sure exactly what this entry
Daniel John Debrunner wrote:
Satheesh Bandaram wrote:
Derby currently doesn't support WITH GRANT OPTION. So, while it is OK
for 'mamta2' here to create the view, an error *should be* raised if
this user attempts to grant access to columns derived from user 'mamta1'
table.
What's
-taskComponents: SQL
Affects Versions: 10.2.0.0Reporter: Satheesh Bandaram Assigned To: Satheesh Bandaram Fix For: 10.2.0.0
Attachments: DERBY-1543.out, Derby1543.diff Address two remaining sub-tasks: Add warning when sqlAuthorization is on with authentication off: This is a precautionary warning, since
[ http://issues.apache.org/jira/browse/DERBY-1608?page=all ]
Satheesh Bandaram reassigned DERBY-1608:
Assignee: Satheesh Bandaram (was: Deepa Remesh)
I can fix this problem. Some of the newly added SYSFUN builtin functions don't
exist
[
http://issues.apache.org/jira/browse/DERBY-1608?page=comments#action_12424334 ]
Satheesh Bandaram commented on DERBY-1608:
--
Deepa, I did not realize you had this defect assigned to you, until after I
assigned it myself. If you want
[ http://issues.apache.org/jira/browse/DERBY-591?page=all ]
Satheesh Bandaram updated DERBY-591:
Assignee: (was: Satheesh Bandaram)
I am not planning to work on this bug in the short term, so unassigning from
myself.
Several builtin
[ http://issues.apache.org/jira/browse/DERBY-1367?page=all ]
Satheesh Bandaram reassigned DERBY-1367:
Assignee: Satheesh Bandaram
add lang/grantrevoke.java to derbynetclientmats
[ http://issues.apache.org/jira/browse/DERBY-1543?page=all ]
Satheesh Bandaram updated DERBY-1543:
-
Attachment: Derby1543.diff
This patch should address these two left over items in GRANT/REVOKE
implementation. Some implementation notes:
1) Now
[
http://issues.apache.org/jira/browse/DERBY-1543?page=comments#action_12424136 ]
Satheesh Bandaram commented on DERBY-1543:
--
One question I had with selecting hard coded UUIDs for internal system table
indices... How does one generate
I noticed Derby currently allows granting non-SELECT privileges to
VIEWs. I will checks to disable this and add some tests.
Satheesh
ij create view myView as select * from newTab;
0 rows inserted/updated/deleted
ij grant *insert *on myView to Sammy;
0 rows inserted/updated/deleted
ij grant
[
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
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
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,
[
http://issues.apache.org/jira/browse/DERBY-1592?page=comments#action_12423680 ]
Satheesh Bandaram commented on DERBY-1592:
--
This functionality is not supported. If a table level privilege has been
granted, revoking part
[
http://issues.apache.org/jira/browse/DERBY-1544?page=comments#action_12423717 ]
Satheesh Bandaram commented on DERBY-1544:
--
Changes to update database owner is already present in Derby upgrade
process it seems there is a defect
[
http://issues.apache.org/jira/browse/DERBY-1521?page=comments#action_12423744 ]
Satheesh Bandaram commented on DERBY-1521:
--
I seem to have missed one of Dan's questions about GRANT REVOKE in this entry:
* Add basic tests to test
[ http://issues.apache.org/jira/browse/DERBY-1592?page=all ]
Satheesh Bandaram resolved DERBY-1592.
--
Resolution: Invalid
Reporter of this defect agreed this is expected behavior. I will update
functional spec to cover this issue, so it becomes
[ http://issues.apache.org/jira/browse/DERBY-1592?page=all ]
Satheesh Bandaram closed DERBY-1592.
Assignee: Satheesh Bandaram
Update statement is allowed to execute even though the column that the
statement access has been revoked
[
http://issues.apache.org/jira/browse/DERBY-1543?page=comments#action_12423757 ]
Satheesh Bandaram commented on DERBY-1543:
--
What is the failure you are seeing with synonyms? Attempting to GRANT or REVOKE
privileges to synonyms should
Thanks for creating this GrantRevoke notes, Dan. Here are some comments
on some of your points.
http://wiki.apache.org/db-derby/GrantRevokeImplementation
1) PrivilegeInfo looks very much like a constant action, the constant
action for grant/revoke is more or less just an empty object that
[ http://issues.apache.org/jira/browse/DERBY-1543?page=all ]
Satheesh Bandaram updated DERBY-1543:
-
Attachment: DERBY-1543.out
This (temp) patch addresses both these remaining issues. Some work is needed to
complete this patch... including 1
[ http://issues.apache.org/jira/browse/DERBY-1538?page=all ]
Satheesh Bandaram reassigned DERBY-1538:
Assignee: Satheesh Bandaram
Unexpected behavior on self privilege revocation
[ http://issues.apache.org/jira/browse/DERBY-1532?page=all ]
Satheesh Bandaram resolved DERBY-1532.
--
Resolution: Invalid
As mentioned, GRANTOR is already part of the primary key in all three new
system catalogs. Information in the functional spec
[ http://issues.apache.org/jira/browse/DERBY-1532?page=all ]
Satheesh Bandaram closed DERBY-1532.
Add GRANTOR column to primary key for SYSTABLEPERMS, SYSCOLPERMS and
SYSROUTINEPERMS
[ http://issues.apache.org/jira/browse/DERBY-464?page=all ]
Satheesh Bandaram updated DERBY-464:
Attachment: grantRevokeSpec_v3.html
Updated functional spec... Changes from v2 version are:
1) Added GRANTOR column to primary key to new system tables
[
http://issues.apache.org/jira/browse/DERBY-464?page=comments#action_12423197 ]
Satheesh Bandaram commented on DERBY-464:
-
Should this issue be marked as RESOLVED? This JIRA entry covers main
GRANT/REVOKE functionality being developed
[ http://issues.apache.org/jira/browse/DERBY-464?page=all ]
Satheesh Bandaram updated DERBY-464:
Fix Version/s: 10.2.0.0
Enhance Derby by adding grant/revoke support. Grant/Revoke provide finner
level of privileges than currently provided
[
http://issues.apache.org/jira/browse/DERBY-1543?page=comments#action_12423198 ]
Satheesh Bandaram commented on DERBY-1543:
--
Good point, Dan. I will address this in my final version of the patch.
Address two remaining issues
[ http://issues.apache.org/jira/browse/DERBY-1023?page=all ]
Satheesh Bandaram resolved DERBY-1023.
--
Resolution: Won't Fix
Not part of the functional spec being targetted for 10.2 release. Might still
be useful enhancement to Derby. If someone has
[ http://issues.apache.org/jira/browse/DERBY-1023?page=all ]
Satheesh Bandaram closed DERBY-1023.
Add EXTERNAL SECURITY DEFINER and EXTERNAL SECURITY INVOKER support for
routines(functions or procedures
[ http://issues.apache.org/jira/browse/DERBY-1543?page=all ]
Satheesh Bandaram reassigned DERBY-1543:
Assignee: Satheesh Bandaram
I have a patch that is partial. Will post final complete patch soon.
Address two remaining issues with GRANT
[ http://issues.apache.org/jira/browse/DERBY-1532?page=all ]
Satheesh Bandaram reassigned DERBY-1532:
Assignee: Satheesh Bandaram
Add GRANTOR column to primary key for SYSTABLEPERMS, SYSCOLPERMS and
SYSROUTINEPERMS
[
http://issues.apache.org/jira/browse/DERBY-1532?page=comments#action_12422934 ]
Satheesh Bandaram commented on DERBY-1532:
--
I was trying to address this issue, but I found that system tables in question
already have GRANTOR
[
http://issues.apache.org/jira/browse/DERBY-1532?page=comments#action_12422935 ]
Satheesh Bandaram commented on DERBY-1532:
--
If there are no more issues or comments with this sub-task, I will will close
it on Monday.
Add GRANTOR
[
http://issues.apache.org/jira/browse/DERBY-147?page=comments#action_12422749 ]
Satheesh Bandaram commented on DERBY-147:
-
Last time this patch was reviewed, there was also another concern about truely
ambigious columns, like:
Select
[
http://issues.apache.org/jira/browse/DERBY-781?page=comments#action_12422753 ]
Satheesh Bandaram commented on DERBY-781:
-
I think it would be good to modify this improvement description, as it will
likely be picked up by release notes
Hi Rick,
It would be good to cover upgrade testing too. There is one known issue
with upgrade and GRANT/REVOKE. I will file a JIRA entry for that. During
database upgrade for a database from 10.1 to 10.2, the owner the
database should change from peudo-user 'DBA' to actual authorizationID
of the
Versions: 10.2.0.0
Reporter: Satheesh Bandaram
Fix For: 10.2.0.0
Address two remaining sub-tasks:
Add warning when sqlAuthorization is on with authentication off: This is a
precautionary warning, since sqlAuthorization doesn't mean much without
authentication being
[
http://issues.apache.org/jira/browse/DERBY-1538?page=comments#action_12422308 ]
Satheesh Bandaram commented on DERBY-1538:
--
Hi Yip... Dan had asked this question long time ago during spec reviews and I
had proposed at that time
[
http://issues.apache.org/jira/browse/DERBY-1542?page=comments#action_12422309 ]
Satheesh Bandaram commented on DERBY-1542:
--
This is still pending development task. I had sent several messages to derbyDev
about two remaining tasks
: 10.2.0.0
Environment: generic
Reporter: Satheesh Bandaram
Fix For: 10.2.0.0
Upgrading a database from 10.1 to 10.2 should automatically change database
owner, recorded as owner of system schemas in sysschemas, from pseudo user
'DBA' to authorizationID of the user
[
http://issues.apache.org/jira/browse/DERBY-1357?page=comments#action_12422336 ]
Satheesh Bandaram commented on DERBY-1357:
--
Submitted this patch. Thanks for documenting the changes very well!
Sendingcompile\OptimizerImpl.java
Daniel John Debrunner wrote:
Isn't the point of Google summer of code to introduce students to open
source development, and this switch to ddlutils and additonal community
involvement is typical of open source? Scratch your own itch but also
benefit the community as well.
Dan
I am all for
Rick Hillegas wrote:
At one point I was keen on re-enabling the national string types. Now
I am leaning toward implementing the ANSI collation language. I think
this is more powerful. In particular, it lets you support more than
one language-sensitive ordering in the same database.
I also
Jean T. Anderson wrote:
One thing to consider is DdlUtils is database agnostic. For example,
adding support for create view doesn't mean just adding it for Derby,
but also adding it for every database supported (see the list at
http://db.apache.org/ddlutils/database-support.html ).
This is
[
http://issues.apache.org/jira/browse/DERBY-533?page=comments#action_12420746 ]
Satheesh Bandaram commented on DERBY-533:
-
I earlier had some interest in enabling national characters for 10.2, but after
dates for 10.2 became clearer, I decided
I will start to review these patches with the goal of committing them.
If anyone has comments or suggestions, please share with the group...
Satheesh
Army wrote:
I posted two patches for some optimizer changes a little over a week
ago: one for DERBY-781 and one for DERBY-1357.
Has anyone
[ http://issues.apache.org/jira/browse/DERBY-242?page=all ]
Satheesh Bandaram closed DERBY-242:
---
Fix has been in the codeline for sometime.
DatabaseMetaData.supportsGetGeneratedKeys needs to return FALSE, since Derby
only has limited support
[ http://issues.apache.org/jira/browse/DERBY-335?page=all ]
Satheesh Bandaram closed DERBY-335:
---
This new feature has been in Derby since 10.1.
Enhance Derby by adding SYNONYM support. A synonym is an alternate name for a
view or a table
Have you considered using PROVIDERFINDER that is part of dependency system? TableDescriptor, for example, stores column list that a view depends on using ColumnsInTable finder. A similar mechanism might work for TablePermDescriptor.
SatheeshOn 7/10/06, Mamta Satoor [EMAIL PROTECTED] wrote:
Hi,
I
for the most part.I still need to cleanup the code, add more errormessages, more compile time checks and tests (all thefun stuff) before its ready for checkin. What is the
timeframe for getting things into 10.2?m--- Satheesh Bandaram [EMAIL PROTECTED] wrote: Hi Manish, Do you have any updates on your
I don't see ICLAs of three summer of code students recorded at Apache.
(http://people.apache.org/~jim/committers.html) Not sure if the students
have sent ICLAs or not, but I think this is a required step and it may
be difficult to track them after their project is done. Would the
students consider
Hi Bryan,
Thanks for working on this long requested feature. More below...
Bryan Pendleton wrote:
Does it seem correct that:
a) RESTRICT processing should consider an index on a column to be
a dependent object and fail the DROP COLUMN if the column is used
in an index?
What happens when
behavior for isEquivalent is going to be for each
class.
Just wanted to swing this proposal by people more familiar with the
code. If you see anything wrong in this proposal, let me know. I'll
probably start on it in a day or two.
cheers
Manish
On 5/23/06, *Satheesh Bandaram* [EMAIL
Great document and good comments from David. I think it would be good to follow ddlUtils approach (approach 2) if feasible. Ramin, should this approach be also discussed on ddlUtils development alias?I think you would need to handle some database objects like CHECK constraints and others in a
Rick, I have been on vacation and later this week I will be at ApacheCon Europe. Looks like I have been missing lots of *fun* about release dates, JDBC4 and other discussions.About Grant/Revoke, one big missing piece (Definer authorization model) is being worked on by Mamta Satoor. She should
I have been seeing this test fail on JDK13 platforms, both SUN and IBM
JVMs since the test was committed. Tomohito, do you have access to JDK13
platform and have interest to fix this failure? If not, I can help.
Satheesh
[bandaram:satheesh] svn log OutBufferedStream.out
*Good *write up! I am not a big fan of silently ignoring user specified
value, even if specified incorrectly. I would vote for filing a big to
correct two issues 1) Checking for less than Integer.MAX_VALUE value
after multiplying specified value by 1024 and 2) Raising an error for
negative values.
Bernt M. Johnsen wrote:
Is it possible to get some synergy between this project and ddl-utils?
(See http://db.apache.org/derby/integrate/db_ddlutils.html)
Right... Jean and myself were just looking at ddlUtils yesterday and
forwarded relavent links to Ramin. This will be looked at during
Rick Hillegas wrote:
hose operations are:
* (all indexes) When you execute SYSCS_UTIL.SYSCS_COMPRESS_TABLE.
* (index only) When you drop a column that is part of a table's
index; the statistics for the affected index are dropped, and
statistics for the other indexes on the table are
Rick Hillegas wrote:
If memory use is not a problem for your environment, set this
property to a high number; allowing the optimizer the maximum
flexibility in considering a join strategy queries involving large
queries leads to better performance. It can also be set to smaller
values for
[ http://issues.apache.org/jira/browse/DERBY-464?page=all ]
Satheesh Bandaram updated DERBY-464:
Derby Info: (was: [Patch Available])
Enhance Derby by adding grant/revoke support. Grant/Revoke provide finner
level of privileges than currently
[
http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415387 ]
Satheesh Bandaram commented on DERBY-1384:
--
While I still don't know if this change is good or not for Derby at this time,
change in max length, if applied, should
[ http://issues.apache.org/jira/browse/DERBY-1329?page=all ]
Satheesh Bandaram updated DERBY-1329:
-
Derby Info: (was: [Patch Available])
Submitted this patch to 10.1 branch. Please resolve and/or close accordingly.
ASSERT failure
[
http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415410 ]
Satheesh Bandaram commented on DERBY-1384:
--
Here is one situation where changing default max length would cause problem. In
soft upgrade, if some one creates
[
http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415433 ]
Satheesh Bandaram commented on DERBY-1384:
--
This is the case I was thinking about. I have coded my application without
specifying lengths for BLOB/CLOB. I would
[
http://issues.apache.org/jira/browse/DERBY-1327?page=comments#action_12415458 ]
Satheesh Bandaram commented on DERBY-1327:
--
I was reviewing this change and I noticed we are moving this:
- /* NOTE: We use the autoincColumn variable
[
http://issues.apache.org/jira/browse/DERBY-1365?page=comments#action_12415056 ]
Satheesh Bandaram commented on DERBY-1365:
--
Submitted this patch to trunk and 10.1 branches. Thanks Army.
Address potential problems with optimizer logic in some
[
http://issues.apache.org/jira/browse/DERBY-1329?page=comments#action_12414557 ]
Satheesh Bandaram commented on DERBY-1329:
--
Submitted this patch to trunk. If you have interest in putting this patch into
10.1.3, please post a 10.1 patch. Looks
[
http://issues.apache.org/jira/browse/DERBY-655?page=comments#action_12414558 ]
Satheesh Bandaram commented on DERBY-655:
-
This patch is committed to trunk and 10.1. Please RESOLVE and close accordingly.
getImportedKeys returns duplicate rows
1 - 100 of 929 matches
Mail list logo