[jira] Created: (DERBY-3971) select * from new SPACETABLE ('tablename') t; throws an error

2008-12-03 Thread Mayuresh Nirhali (JIRA)
select * from new SPACETABLE ('tablename') t; throws an error --- Key: DERBY-3971 URL: https://issues.apache.org/jira/browse/DERBY-3971 Project: Derby Issue Type: Bug Affects

[jira] Commented: (DERBY-637) Conglomerate does not exist after inserting large data volume

2008-11-19 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648965#action_12648965 ] Mayuresh Nirhali commented on DERBY-637: I recently saw the same error while doing a

[jira] Commented: (DERBY-2592) Wrong description of IndexName field in public JavaDoc for LockTable

2008-01-29 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12563512#action_12563512 ] Mayuresh Nirhali commented on DERBY-2592: - Jazarine, On a quick look at your

[jira] Commented: (DERBY-2602) TIMESTAMP value is truncated when return to client

2007-11-15 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542771 ] Mayuresh Nirhali commented on DERBY-2602: - A quick look at client/amt/PreparedStatement:setTimestamp(int

[jira] Assigned: (DERBY-2602) TIMESTAMP value is truncated when return to client

2007-11-15 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali reassigned DERBY-2602: --- Assignee: Mayuresh Nirhali TIMESTAMP value is truncated when return to client

[jira] Updated: (DERBY-2017) Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length

2007-10-25 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2017: Assignee: (was: Mayuresh Nirhali) Cathey, I am not working on this issue. Currently, I

[jira] Updated: (DERBY-1201) ResultSet.updateRow() in network client should not throw an exception if no fields in the row have been modified.

2007-06-08 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-1201: Attachment: TestUpdateRow.java This issue is reproducible on 10.2.2, but not on 10.3

[jira] Commented: (DERBY-2017) Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length

2007-06-08 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502750 ] Mayuresh Nirhali commented on DERBY-2017: - Thanks a lot Narayanan and Knut. After some more investigation,

[jira] Updated: (DERBY-2017) Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length

2007-06-04 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2017: Attachment: derby2017_try1.diff This is a HIGH VALUE FIX CANDIDATE. I did some more

[jira] Assigned: (DERBY-2017) Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length

2007-06-04 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali reassigned DERBY-2017: --- Assignee: Mayuresh Nirhali Client driver can insert and commit partial data when a

[jira] Commented: (DERBY-2017) Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length

2007-06-04 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501180 ] Mayuresh Nirhali commented on DERBY-2017: - Thanks narayanan for your comments. As I mentioned earlier, this

[jira] Closed: (DERBY-1345) net/Request.writeScalarStream() simply prints stack trace on encryption exception

2007-06-04 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali closed DERBY-1345. --- Resolution: Invalid Assignee: Mayuresh Nirhali fix of Derby-1388 makes this issue

[jira] Commented: (DERBY-2386) timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals

2007-05-28 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499499 ] Mayuresh Nirhali commented on DERBY-2386: - ReleaseNote looks good. Thanks myrna for taking care of this!

[jira] Updated: (DERBY-1355) ClientDriver ResultSetMetaData.isAutoIncrement(column) always returns false

2007-05-24 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-1355: Attachment: derby1355_testv1.diff Created another patch for the test changes. Updated

[jira] Updated: (DERBY-1355) ClientDriver ResultSetMetaData.isAutoIncrement(column) always returns false

2007-05-24 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-1355: Derby Info: [Patch Available] Fix Version/s: 10.3.0.0 10.2.3.0

[jira] Commented: (DERBY-1355) ClientDriver ResultSetMetaData.isAutoIncrement(column) always returns false

2007-05-23 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498206 ] Mayuresh Nirhali commented on DERBY-1355: - derbyall and Suites.All ran fine. I will now look into adding a

[jira] Updated: (DERBY-1355) ClientDriver ResultSetMetaData.isAutoIncrement(column) always returns false

2007-05-18 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-1355: Attachment: derby1355_v1.diff I have created a quick patch for this. It is evident from

[jira] Assigned: (DERBY-1355) ClientDriver ResultSetMetaData.isAutoIncrement(column) always returns false

2007-05-17 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali reassigned DERBY-1355: --- Assignee: Mayuresh Nirhali ClientDriver ResultSetMetaData.isAutoIncrement(column)

[jira] Updated: (DERBY-2549) ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE

2007-05-15 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2549: Attachment: derby2549_testv1.diff I have added another test to

[jira] Updated: (DERBY-2549) ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE

2007-05-15 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2549: Derby Info: [Patch Available] Fix Version/s: 10.3.0.0 10.2.3.0

[jira] Updated: (DERBY-2230) AssertFailure: ByteCode Conditional then/else stack mismatch

2007-05-15 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2230: Attachment: derby2230_testv1.diff patch adds another testcase to GroupByExpressionTest for

[jira] Updated: (DERBY-2230) AssertFailure: ByteCode Conditional then/else stack mismatch

2007-05-15 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2230: Derby Info: [Patch Available] AssertFailure: ByteCode Conditional then/else stack

[jira] Updated: (DERBY-2549) ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE

2007-05-14 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2549: Attachment: derby2549_v3.diff Thanks Mike for your expert comments. I realized that '--'

[jira] Commented: (DERBY-2549) ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE

2007-05-14 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495573 ] Mayuresh Nirhali commented on DERBY-2549: - derbyall and Suites_All did NOT show any new failures for the

[jira] Commented: (DERBY-2549) ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE

2007-05-11 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494970 ] Mayuresh Nirhali commented on DERBY-2549: - Thanks Mike for clarifying the behavior. On a second thought,

[jira] Updated: (DERBY-2549) ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE

2007-05-11 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2549: Attachment: derby2549_v2.diff I have created a new patch, derby2549_v2.diff. This change

[jira] Assigned: (DERBY-2425) ResultSetMetaData.getColumnDisplaySize() returns a negative value for BLOB columns for client

2007-04-25 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali reassigned DERBY-2425: --- Assignee: Mayuresh Nirhali ResultSetMetaData.getColumnDisplaySize() returns a

[jira] Updated: (DERBY-2425) ResultSetMetaData.getColumnDisplaySize() returns a negative value for BLOB columns for client

2007-04-25 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2425: Attachment: derby2425.diff I have created a patch for this bug. It is very trivial, I

[jira] Updated: (DERBY-2425) ResultSetMetaData.getColumnDisplaySize() returns a negative value for BLOB columns for client

2007-04-25 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2425: Derby Info: [Patch Available] Fix Version/s: 10.3.0.0

[jira] Commented: (DERBY-2549) ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE

2007-04-25 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491873 ] Mayuresh Nirhali commented on DERBY-2549: - You might want to look at Derby-606. The testcases that were

[jira] Commented: (DERBY-595) Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases

2007-04-18 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489677 ] Mayuresh Nirhali commented on DERBY-595: derbyall and junit tests passed. Patch is ready for review!!

[jira] Updated: (DERBY-595) Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases

2007-04-17 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-595: --- Attachment: derby595_v2.diff Kristian, I have tried to address your comments in this next

[jira] Updated: (DERBY-2230) AssertFailure: ByteCode Conditional then/else stack mismatch

2007-04-17 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2230: Derby Info: [Patch Available] Fix Version/s: 10.3.0.0 derbyall, suites.All runs did

[jira] Commented: (DERBY-2166) Implement proper handling of SocketTimeoutException in DRDAConnThread

2007-04-16 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489029 ] Mayuresh Nirhali commented on DERBY-2166: - The fix to the parent issue Derby-1856 was ported to 10.2 and

[jira] Resolved: (DERBY-2386) timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals

2007-04-12 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali resolved DERBY-2386. - Resolution: Fixed No issues found on the fix. timestampdiff function fails when using

[jira] Commented: (DERBY-2230) AssertFailure: ByteCode Conditional then/else stack mismatch

2007-04-12 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488395 ] Mayuresh Nirhali commented on DERBY-2230: - The assert is reproducible on trunk as well. When I tried the

[jira] Commented: (DERBY-2230) AssertFailure: ByteCode Conditional then/else stack mismatch

2007-04-10 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487794 ] Mayuresh Nirhali commented on DERBY-2230: - I did NOT see any assert failures when I ran on the latest trunk.

[jira] Updated: (DERBY-2230) AssertFailure: ByteCode Conditional then/else stack mismatch

2007-04-10 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2230: Fix Version/s: 10.2.2.1 AssertFailure: ByteCode Conditional then/else stack mismatch

[jira] Assigned: (DERBY-2230) AssertFailure: ByteCode Conditional then/else stack mismatch

2007-04-10 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali reassigned DERBY-2230: --- Assignee: Mayuresh Nirhali AssertFailure: ByteCode Conditional then/else stack

[jira] Commented: (DERBY-2166) Implement proper handling of SocketTimeoutException in DRDAConnThread

2007-04-09 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487513 ] Mayuresh Nirhali commented on DERBY-2166: - I downloaded the repro and tried it on latest trunk. The repro

[jira] Updated: (DERBY-595) Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases

2007-04-09 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-595: --- Derby Info: [Patch Available] Fix Version/s: 10.3.0.0 10.2.3.0

[jira] Updated: (DERBY-595) Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases

2007-04-06 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-595: --- Attachment: derby595.diff Attaching patch for review with this comment. The implementation

[jira] Commented: (DERBY-595) Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases

2007-04-03 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486316 ] Mayuresh Nirhali commented on DERBY-595: Thanks Kristian. I agree with you that implementing getTraceString

[jira] Updated: (DERBY-2386) timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals

2007-03-15 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2386: Attachment: derby2386-v2.diff Thanks Dan for the clarification. I have created a new

[jira] Updated: (DERBY-2386) timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals

2007-03-08 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2386: Attachment: derby2386.diff I concur. I think it will help if return value is BigInt. I

[jira] Updated: (DERBY-2386) timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals

2007-03-08 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2386: Derby Info: [Patch Available] Fix Version/s: 10.3.0.0 10.2.3.0

[jira] Assigned: (DERBY-595) Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases

2007-03-07 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali reassigned DERBY-595: -- Assignee: Mayuresh Nirhali Using derby.language.logStatementText=true can mask certain

[jira] Commented: (DERBY-595) Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases

2007-03-07 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479234 ] Mayuresh Nirhali commented on DERBY-595: After some debugging, I found that the call to getString returns the

[jira] Assigned: (DERBY-2386) timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals

2007-03-05 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali reassigned DERBY-2386: --- Assignee: Mayuresh Nirhali timestampdiff function fails when using

[jira] Commented: (DERBY-2220) Uncommitted transactions executed throught XAResource will held locks after the application terminates (or crashes during the transaction).

2007-03-05 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478263 ] Mayuresh Nirhali commented on DERBY-2220: - Prashant, The patch has not made to the derby codebase yet. It

[jira] Updated: (DERBY-2220) Uncommitted transactions executed throught XAResource will held locks after the application terminates (or crashes during the transaction).

2007-03-05 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2220: Comment: was deleted Uncommitted transactions executed throught XAResource will held

[jira] Commented: (DERBY-2386) timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals

2007-03-05 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478275 ] Mayuresh Nirhali commented on DERBY-2386: - The SQL_TSI_FRAC_SECOND type is used for fractional timestamp

[jira] Updated: (DERBY-2103) After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.

2007-01-23 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2103: Attachment: Derby2103_v3.diff I have attached version 3 of this patch modifying comments.

[jira] Updated: (DERBY-2103) After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.

2007-01-18 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2103: Attachment: derby2103.diff After a Lexical Error due to syntax error ,even a simple

[jira] Commented: (DERBY-2103) After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.

2007-01-18 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465742 ] Mayuresh Nirhali commented on DERBY-2103: - I figured that there is a better way to fix this issue by

[jira] Updated: (DERBY-2103) After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.

2007-01-18 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2103: Derby Info: [Patch Available] Fix Version/s: 10.2.3.0 After a Lexical Error due to

[jira] Updated: (DERBY-2103) After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.

2007-01-18 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali updated DERBY-2103: Attachment: derby2103_v2.diff After a Lexical Error due to syntax error ,even a

[jira] Commented: (DERBY-2103) After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.

2007-01-18 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465783 ] Mayuresh Nirhali commented on DERBY-2103: - uploading a new patch with comments for the code change. please

[jira] Commented: (DERBY-2103) After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.

2007-01-18 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465948 ] Mayuresh Nirhali commented on DERBY-2103: - Thanks Dag! I have raised this with javacc (issue-152). So, does

[jira] Commented: (DERBY-2103) After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.

2007-01-16 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465141 ] Mayuresh Nirhali commented on DERBY-2103: - derbyall testrun just finished with the proposed fix and it did

[jira] Assigned: (DERBY-2103) After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.

2007-01-15 Thread Mayuresh Nirhali (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayuresh Nirhali reassigned DERBY-2103: --- Assignee: Mayuresh Nirhali After a Lexical Error due to syntax error ,even a

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-12-07 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: derby606_impl-v6.diff new patch for the implementation is attached. I had some problems with svn:eol settings and they have been fixed now

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-12-07 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: derby606_upgrade-v6.diff As Bryan and others pointed out Derby supports upgrade from 10.1 to 10.3 also. This patch seems to incorrectly

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-12-07 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: derby606_upgrade-v7.diff Suresh pointed out that 10.1 to 10.3 upgrade test will be more appropriate at this time. I think that is wise also

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-12-04 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: derby606_impl-v5.diff derby606_upgrade-v5.diff Thanks Suresh for catching that! I have created new patches based on your

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-12-01 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: derby606-v3.diff Attaching next version of the patch! This version now will work well with 10.2 binaries integrated in the trunk. Another

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-12-01 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: derby606_impl-v4.diff derby606_upgrade-v4.diff Thanks a lot suresh, I think I misunderstood the proposal you gave initially

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-28 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: derby606-v2.diff Attaching next version of patch. This patch now includes changes to the OnlineCompressTest and UpgradeTest. I have created

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-28 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Derby Info: [Patch Available] SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-17 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: derby606_v1.diff I am attaching a preliminary patch. This does not include changes to upgradeTest and also the repro is not added to the

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-17 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Fix Version/s: 10.3.0.0 SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

[jira] Commented: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-17 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=comments#action_12450785 ] Mayuresh Nirhali commented on DERBY-606: I looked at the OnlineCompressTest and realized that to reproduce this case, the simplest way is to increase the

[jira] Commented: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-16 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=comments#action_12450437 ] Mayuresh Nirhali commented on DERBY-606: Thanks Suresh for your comments. I got a little further with the additional Class approach and as you mentioned I

[jira] Commented: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-15 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=comments#action_12450071 ] Mayuresh Nirhali commented on DERBY-606: Thanks Mike and Suresh. Yes. It makes sense to only change the log record format for this special case. Looking

[jira] Commented: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-14 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=comments#action_12449683 ] Mayuresh Nirhali commented on DERBY-606: Thanks mike for looking into this and also for the valuable suggestions. They were really helpful to put me in the

[jira] Assigned: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-10 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali reassigned DERBY-606: -- Assignee: Mayuresh Nirhali SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-11-10 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: A606Test.java Attaching a repro for this issue. The idea for reproduction is to create a table with large number of records and delete most

[jira] Commented: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

2006-10-09 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-606?page=comments#action_12440827 ] Mayuresh Nirhali commented on DERBY-606: I was able to reproduce this error. I am working with 30 million rows of schema mentioned in the previous comments.

[jira] Updated: (DERBY-1072) Misleading/wrong error message while dropping a view

2006-09-07 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1072?page=all ] Mayuresh Nirhali updated DERBY-1072: Attachment: 1072doc_v1.diff 1072doc_v1.zip The bug was found in the documentation in following places,

[jira] Commented: (DERBY-1072) Misleading/wrong error message while dropping a view

2006-09-06 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1072?page=comments#action_12432829 ] Mayuresh Nirhali commented on DERBY-1072: - In the reference documentation, the section 'Interaction with the dependency system' contains an example which

[jira] Updated: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-08-30 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=all ] Mayuresh Nirhali updated DERBY-418: --- Attachment: derby418_v6.diff Thanks Knut, for catching that! I have attached a new patch with changes suggested by Knut, derby418_v6.diff. outofmemory

[jira] Updated: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-08-25 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=all ] Mayuresh Nirhali updated DERBY-418: --- Attachment: derby418_v4.diff Thanks knut and apologies for missing out on indentation guidelines. I have attached another patch integrating both the

[jira] Updated: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-08-24 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=all ] Mayuresh Nirhali updated DERBY-418: --- Attachment: derby418_v2.diff posting another version of the patch here. I have corrected the catch block and now throwing the wrapped exception. This

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-08-22 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429668 ] Mayuresh Nirhali commented on DERBY-418: I tried the approach suggested by Dan in DERBY-1142, and my version of change looks like as below, In

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-08-22 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429709 ] Mayuresh Nirhali commented on DERBY-418: Thanks Knut for pointing that out. I did not mean to provide a patch for this JIRA, but just wanted to try out a

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-08-20 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429259 ] Mayuresh Nirhali commented on DERBY-418: I tried modifying the finalize method of embedResultSet to close singleuseActivation and that seems to have worked

[jira] Commented: (DERBY-1142) Metadata calls leak memory

2006-08-20 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1142?page=comments#action_12429260 ] Mayuresh Nirhali commented on DERBY-1142: - If the singleUseActivation is closed in the finalize method of EmdebResultSet then the memory leak is not

[jira] Assigned: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-08-14 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=all ] Mayuresh Nirhali reassigned DERBY-418: -- Assignee: Mayuresh Nirhali outofmemory error when running large query in autocommit=false mode

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-08-14 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12427891 ] Mayuresh Nirhali commented on DERBY-418: Thanks to Andreas and Oystein for pointing out another possibilty that when the statement objects are GC'd, the

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-08-11 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12427480 ] Mayuresh Nirhali commented on DERBY-418: I used the JHAT (jdk1.6) to dump the java heap and observed that large number of generated objects of type

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

2006-07-20 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12422407 ] Mayuresh Nirhali commented on DERBY-418: I was able to reproduce this issue on my Sol10 x86 jdk1.5 platform. I ran with following option, -verbosegc (java

[jira] Reopened: (DERBY-836) ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for DECIMAL columns

2006-07-17 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ] Mayuresh Nirhali reopened DERBY-836: 3 store tests and 5 nist tests fail due to minor canon file changes. Reopening this issue to make sure those issues are fixed.

[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for DECIMAL columns

2006-07-17 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ] Mayuresh Nirhali updated DERBY-836: --- Attachment: derby836-v7_2.diff regenerated the patch as per andrew's comment. ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for

[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for DECIMAL columns

2006-07-13 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ] Mayuresh Nirhali updated DERBY-836: --- Attachment: derby836-v6.diff Thanks Dan for pointing out the error. I have now added diffs for the master files which were failing due to this change

[jira] Commented: (DERBY-1430) Test parameterMapping.java often fails with DerbyNetClient on Solarisx86

2006-07-13 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1430?page=comments#action_12420882 ] Mayuresh Nirhali commented on DERBY-1430: - Here is my analysis on this issue so far: This bug is seen on jdbcapi/parameterMapping.java (in DerbyNetClient framework)

[jira] Updated: (DERBY-331) create table fails when a constraint defintion follows a column default

2006-06-08 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-331?page=all ] Mayuresh Nirhali updated DERBY-331: --- Fix Version: 10.1.3.0 This bug is 10.1 branch porting candidate for 10.1.3 release. I merged the changes (209842) into my fresh 10.1 branch child. The

[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for DECIMAL columns

2006-06-07 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ] Mayuresh Nirhali updated DERBY-836: --- Attachment: derby836_v5.diff I ran derbyall and found many failures. I ran it today again and still see some failures which does not seem related to

[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for DECIMAL columns

2006-06-06 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ] Mayuresh Nirhali updated DERBY-836: --- Attachment: derby836-v4.diff Thanks daniel for the review. As per the review comments, I have corrected the canon files for odbc_metadata and Upgrade

[jira] Updated: (DERBY-1072) Misleading/wrong error message while dropping a view

2006-05-26 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1072?page=all ] Mayuresh Nirhali updated DERBY-1072: Attachment: derby1072-v4.diff derby1072-v4.stat I was hoping that this patch gets reviewed and committed before. In the past few

[jira] Updated: (DERBY-836) ResultSetMetaData.getColumnDisplaySize sometimes returns wrong values for DECIMAL columns

2006-05-26 Thread Mayuresh Nirhali (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-836?page=all ] Mayuresh Nirhali updated DERBY-836: --- Attachment: derby836-v3.diff This patch was reviewed but not yet commited since last month. In the past few weeks, some files which were part of this

  1   2   >