Re: [jira] [Commented] (DERBY-7091) Times Inserted Incorrectly Around Daylight Savings Time Change in Spring

Hi ij> SELECT * FROM t ORDER BY key_col; KEY_COL|DESC_COL |TS_STRING |TS --- 1 |NULL |2017-03-12 01:48:00.000

Re: [VOTE] Thomas Nielsen as a Derby committer

Bryan Pendleton wrote: I propose that Thomas Nielsen shall be a Derby committer. +1

Re: [VOTE] V. Narayanan as a committer

Rick Hillegas wrote: Please vote on whether we should make V. Narayanan a Derby committer. The polls close at 5:00 pm San Francisco time on Thursday April 10. +1

Re: [VOTE] Jørgen Løland as a committ er

Rick Hillegas wrote: Please vote on whether we should make Jørgen Løland a Derby committer. The polls close at 5:00 pm San Francisco time on Thursday April 10. +1

[jira] Commented: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585440#action_12585440 ] Anurag Shekhar commented on DERBY-3354: --- Thanks Kristian for looking at the patch. I

[jira] Updated: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3354: -- Attachment: derby-3354_v2.diff in derby-3354_v2.diff I have fixed the issues Kristian had

[jira] Updated: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3354: -- Attachment: derby-3354_v3.diff Added localConn.removeLOBMapping in Blob.free BlobClob4BlobTest

[jira] Commented: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585483#action_12585483 ] Anurag Shekhar commented on DERBY-3354: --- Thanks Oystein for pointing out. I missed

[jira] Updated: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3354: -- Attachment: derby-3354_v4.diff Putting remove mapping in else was a mistake. Sorry about

[jira] Commented: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585015#action_12585015 ] Anurag Shekhar commented on DERBY-3354: --- Thanks Øystein for look at the patch. My

[jira] Updated: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3354: -- Attachment: derby-3354_v1.diff Description of derby-3354_v1.diff This patch introduces a new

[jira] Updated: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3354: -- Attachment: derby-3354_preview.diff In this patch I have introduced a WeakHashMap to hold lob

[jira] Commented: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584108#action_12584108 ] Anurag Shekhar commented on DERBY-3354: --- LobMapping and locater is used by the stored

[jira] Updated: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

[ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3523: -- Attachment: derby-3523-upgradetest.diff upgrade tests for modified error messages. sql

[jira] Assigned: (DERBY-3566) Alter column set data type not allowed in soft upgrade with unique constraint

[ https://issues.apache.org/jira/browse/DERBY-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar reassigned DERBY-3566: - Assignee: Anurag Shekhar Alter column set data type not allowed in soft upgrade

[jira] Resolved: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar resolved DERBY-3502. --- Resolution: Fixed Patch committed in revision #634852 There is no outstanding patch

[jira] Closed: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar closed DERBY-3502. - Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[jira] Commented: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

[ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581507#action_12581507 ] Anurag Shekhar commented on DERBY-3523: --- thanks kathey for committing the patch. I

Re: [jira] Created: (DERBY-3566) Alter column set data type not allowed in soft upgrade with unique constraint

It might be because of my work related to unique constraint, I will look into it. anurag Kathey Marsden (JIRA) wrote: In 10.4 soft upgrade mode I cannot: ij create table t0 (i int not null, v varchar(1) not null, constraint uq unique(v,i)); 0 rows inserted/updated/deleted ij alter table t0

[jira] Updated: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

[ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3523: -- Attachment: derby-3523v3.diff I have taken off the new method from standardException and moved

[jira] Updated: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

[ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3523: -- Attachment: derby-3523v1.diff This patch () adds new messages for X0Y63, X0Y63 and X0Y63.S I

[jira] Updated: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

[ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3523: -- Attachment: derby-3523v2.diff Thanks Jorgen for pointing out. Attaching new version (derby

Re: [jira] Commented: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

Project: Derby Issue Type: Bug Affects Versions: 10.4.0.0, 10.5.0.0 Reporter: Anurag Shekhar Assignee: Anurag Shekhar There are three messages which after Derby-3330 checkin now giving wrong information. These are 42831:'{0}' cannot be a column

[jira] Commented: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

[ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577883#action_12577883 ] Anurag Shekhar commented on DERBY-3523: --- I am planning to introduce similar

[jira] Commented: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

[ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577911#action_12577911 ] Anurag Shekhar commented on DERBY-3523: --- I don't think adding information about

[jira] Commented: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

[ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577511#action_12577511 ] Anurag Shekhar commented on DERBY-3523: --- There can be two ways to fix this problem 1

[jira] Created: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

://issues.apache.org/jira/browse/DERBY-3523 Project: Derby Issue Type: Bug Affects Versions: 10.4.0.0, 10.5.0.0 Reporter: Anurag Shekhar Assignee: Anurag Shekhar There are three messages which after Derby-3330 checkin now giving wrong information

[jira] Updated: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3502: -- Attachment: derby-3502v3.diff Description of derby-3502v3.diff fixed the new issue Army had

[jira] Commented: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576292#action_12576292 ] Anurag Shekhar commented on DERBY-3456: --- Thanks Mike for committing it. You have

[jira] Commented: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576311#action_12576311 ] Anurag Shekhar commented on DERBY-3456: --- This error message is thrown while setting

Re: build failure related to Unique Constraints

File is now in. Please update the workspace. anurag Rick Hillegas wrote: I am seeing the following build failure after syncing with the trunk. It looks like a test class was not checked in: [javac]

Re: [jira] Commented: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

you should add a new error message for the new code to use, and soft upgrade can continue to use the old message. This is assuming there is no SQL standard for this exact error number. Anurag Shekhar (JIRA) wrote: [ https://issues.apache.org/jira/browse/DERBY-3456?page

[jira] Updated: (DERBY-3330) provide support for unique constraint over keys that include one or more nullable columns.

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330_followup_1.diff Issues addressed in derby-3330_followup_1.diff

[jira] Created: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.4.0.0 Reporter: Anurag Shekhar Assignee: Anurag Shekhar Unique Constraint now uses non unique backing indexes with new attribute UniqueWithDuplicateNulls. This index has

[jira] Updated: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3502: -- Attachment: derby-3502v1.diff Description of Derby-3502.diff This patch fixes backing index

[jira] Commented: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575740#action_12575740 ] Anurag Shekhar commented on DERBY-3456: --- I have created DERBY-3502 to address issues

[jira] Issue Comment Edited: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

. Key: DERBY-3456 URL: https://issues.apache.org/jira/browse/DERBY-3456 Project: Derby Issue Type: Sub-task Components: SQL, Store Affects Versions: 10.4.0.0 Environment: all Reporter: Anurag Shekhar

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: derby-3456v5.diff Reattaching derby-3456v5.diff to avoid confusion. Allow

[jira] Updated: (DERBY-3330) provide support for unique constraint over keys that include one or more nullable columns.

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: UniqueConstraint_Implementation_V4.html Updated implementation doc Added a section

[jira] Updated: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3502: -- Attachment: derby-3502v2.diff Description of derby-3502v2.diff Moved tests to lang

[jira] Commented: (DERBY-3330) provide support for unique constraint over keys that include one or more nullable columns.

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575862#action_12575862 ] Anurag Shekhar commented on DERBY-3330: --- Thanks Mike for the review. Looks like

[jira] Commented: (DERBY-3330) provide support for unique constraint over keys that include one or more nullable columns.

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575863#action_12575863 ] Anurag Shekhar commented on DERBY-3330: --- looking at it more carefully, would

[jira] Updated: (DERBY-3330) provide support for unique constraint over keys that include one or more nullable columns.

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: sortercomments.diff Added comments in UniqueWithDuplicateNullsMergeSort.java

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: derby-3456-Tests_v2.diff derby-3456-Tests_v2.diff Fixed conflicts with latest svn

[jira] Commented: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576053#action_12576053 ] Anurag Shekhar commented on DERBY-3456: --- upgrade and other tests are included in test

[jira] Commented: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575325#action_12575325 ] Anurag Shekhar commented on DERBY-3456: --- thanks Army for looking at the patch testing

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: derby-3456v4.diff This patch fixes issues related to unique constraint using

[jira] Commented: (DERBY-3330) provide support for unique constraint over keys that include one or more nullable columns.

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575436#action_12575436 ] Anurag Shekhar commented on DERBY-3330: --- CreateIndexConstantAction.java - use

[jira] Commented: (DERBY-3330) provide support for unique constraint over keys that include one or more nullable columns.

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575079#action_12575079 ] Anurag Shekhar commented on DERBY-3330: --- Thanks Mike for guiding me through

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: derby-3456-Tests.diff derby-3456v3.diff Description of derby

[jira] Updated: (DERBY-3330) provide support for unique constraint over keys that include one or more nullable columns.

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330-UpgradeTests.diff description of derby-3330-UpgradeTests.diff

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Derby Info: [Patch Available, Release Note Needed] provide support for unique constraint over

[jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573671#action_12573671 ] Anurag Shekhar commented on DERBY-3330: --- junit.all and derbyall tests are running

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: derby-3456v2.diff derby-3456v2.diff updated to work with latest patch for DERBY

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: db2Compatibility-v2.diff description of db2Compatibility-v2.diff removed test

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330v11.diff Description of patch (derby-3330v11.diff) Now the backing

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: db2Compatibility.diff db2Compatibility.diff diff file to update

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: altertable.diff setnulltest.diff I have run derbyall harness

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330v12.diff derby-3330v12.diff fixed indentation issues and added comment

[jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573365#action_12573365 ] Anurag Shekhar commented on DERBY-3330: --- UniqueWithDuplicateNulls explains the actual

[jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573369#action_12573369 ] Anurag Shekhar commented on DERBY-3330: --- uniqueWhenNotNull attribute (in B2I

[jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573450#action_12573450 ] Anurag Shekhar commented on DERBY-3330: --- please ignore derby-3330v12.diff . It had

failures in org.apache.derbyTesting.functionTests.tests.lang.LangScripts

I am seeing some failures in LangScripts tests in my fresh workspace. Is some one else also experiencing failures ? I am running SUN jdk1.6 on linux. thanks anurag

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330v13.diff changes in derby-3330v13.diff 1. replaced uniqueWhenNotNull

unique constraint and db2 compatibility tests

After enabling unique constraint on nullable fields db2 compatibility tests are failing because they expect failure while creating unique constraint over null able fields. For now I have modified the out file (Attached separately in DERBY-3330, db2Compatibility.diff ) Is it right thing to do ?

Re: hi,may I ask something about store layer of Derby

you can find few papers on store here http://db.apache.org/derby/papers/index.html#Derby+Engine anurag 那贵鹏 wrote: hi,may I ask something about store layer of Derby? I want to learn the architecture of store layer . for Example, Class Diagram and relations and how the data is stored in what

[jira] Created: (DERBY-3474) update unique constraint sections of refrence manual

: 10.4.0.0 Reporter: Anurag Shekhar Derby-3330 adds support for unique constraint over null able fields. Derby refrence manual should be updated to include it while explaining about unique constraint. -- This message is automatically generated by JIRA. - You can reply to this email to add

[jira] Updated: (DERBY-3474) update unique constraint sections of refrence manual

[ https://issues.apache.org/jira/browse/DERBY-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3474: -- Attachment: derby-3474.diff I have updated relevant sections of dita sources to include

[jira] Created: (DERBY-3473) write test cases to test locking during tree operation

: 10.4.0.0 Reporter: Anurag Shekhar Assignee: Anurag Shekhar Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

[jira] Updated: (DERBY-3473) write test cases to test locking during tree operation

[ https://issues.apache.org/jira/browse/DERBY-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3473: -- Attachment: derby-3473.diff This patch has test case to test insert while the record

Re: [jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

if the index is accessed for the first time, as the contain information is otherwise cached. It is important to test that the new formatid stuff is being read from DISK correctly. Also how have you been testing your retry code? Anurag Shekhar (JIRA) wrote: [ https://issues.apache.org

[jira] Commented: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573031#action_12573031 ] Anurag Shekhar commented on DERBY-3456: --- After applying 3330. A unique constraint

[jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573032#action_12573032 ] Anurag Shekhar commented on DERBY-3330: --- dml019 test group by clause of unique

Re: [jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

of unique constraint on non-nullable columns would be unchanged. So this constraint should still be backed by a unique index. Anurag Shekhar (JIRA) wrote: [ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId

Re: [jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

Neighter the sql spec nor the derby manual promises this behavior (ordering of group by clause without order by). So I don't think this is a deviation from the existing behavior. anurag Anurag shekhar wrote: Unique constraint on non nullable fields still act like a unique index (because

Re: [jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

constraint. o future index optimization may not apply, there are some compression techniques that lend themselves better to unique indexes vs. non-unique. o others i have not thought of. Anurag shekhar wrote: Unique constraint on non nullable fields still act like a unique index (because

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: upgradetests_v2.diff This patch contains additional tests to test indexes created

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330v10.diff Changes in this (derby-3330v10.diff) patch since (derby-3330v9

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: upgradetests.diff This patch has upgrade tests for unique constraint. under soft

Re: 10.4 Feature Freeze

[EMAIL PROTECTED] wrote: ... is fast approaching (2008-02-29) Is this still a reasonable date, or should we consider delaying it? Unique constraints On track I have all the patches (3 of them) in jira and there are chances that they might get commited before 29th but having one

Re: [jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

Army wrote: I haven't been following this discussion at all, but for what it's worth, this same sort of question came up in the context of DERBY-3299. I went with the simple approach of dropping the old index and creating the new one, so some logic for that kind of thing is now in the 10.4

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: derby-3456v1.diff derby-3456v1.diff enables setting columns (if they are part

[jira] Commented: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572243#action_12572243 ] Anurag Shekhar commented on DERBY-3456: --- This patch should be applied after applying

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330v9.diff I have removed hard upgrade code from derby-3330v9.diff. Now

[jira] Created: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

Type: Sub-task Components: SQL, Store Affects Versions: 10.4.0.0 Environment: all Reporter: Anurag Shekhar Assignee: Anurag Shekhar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: UniqueConstraint_Implementation_V3.html updated hard upgrade section. provide

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330v7.diff This page include the code to scan multiple slot/page

Re: [jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

the fields participating in unique constraint (to achieve new behaviou from the existing constraints) . Anurag Shekhar (JIRA) wrote: [ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330v8.diff In this patch (derby-3330v8.diff) I have modified upgrade

Re: [jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

that exist should only be on non-nullable columns so should not need to be changed. I have not read through the new code yet, but I assume also that new constraints on non-nullable columns also don't use the new code - they should not pay the left/right search cost. Anurag Shekhar (JIRA) wrote

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: UniqueConstraint_Implementation_V2.html Updated version Implementation Details

Re: [jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

Army wrote: Mike Matrigali wrote: This would mean either dropping/recreating the index at alter time or adding a new store interface to convert from old index type to new index type. I haven't been following this discussion at all, but for what it's worth, this same sort of question came up

Re: [jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

Mike Matrigali wrote: Anurag shekhar wrote: Army wrote: Mike Matrigali wrote: This would mean either dropping/recreating the index at alter time or adding a new store interface to convert from old index type to new index type. I haven't been following this discussion at all, but for what

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330v6.diff This patch includes hard upgrade (Upgrade test from 10.3.1.4

[jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569987#action_12569987 ] Anurag Shekhar commented on DERBY-3330: --- Thanks Mike for pointing out the possibility

[jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568850#action_12568850 ] Anurag Shekhar commented on DERBY-3330: --- Details about changes in java/engine/org

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: derby-3330v5.diff This patch includes following changes since v4 1. Fixed

[jira] Commented: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568879#action_12568879 ] Anurag Shekhar commented on DERBY-3330: --- Impact of isolation level The records

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: UniqueConstraint_Implementation.html Attaching the implementation documents. I

[jira] Updated: (DERBY-3330) provide support for unique constraint over nullable columns

[ https://issues.apache.org/jira/browse/DERBY-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3330: -- Attachment: BTreeController.diff Thanks Mike in taking time to explain the nuances of locking

  1   2   3   4   5   >