[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

[ https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2017: Assignee: (was: Saurabh Vyas) I will not be working on this anymore, so un-assigning myself

[jira] Commented: (DERBY-2605) You can create BOOLEAN columns in 10.3

[ https://issues.apache.org/jira/browse/DERBY-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495454 ] Saurabh Vyas commented on DERBY-2605: - Hi James, your patch adds NATIONAL CHAR types also where as these are not

[jira] Updated: (DERBY-2280) DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column returns incorrect information for BLOB CLOB data type

[ https://issues.apache.org/jira/browse/DERBY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2280: Attachment: Derby-2280_v2.diff Attached the new patch with comments from Army Kathey

[jira] Commented: (DERBY-2280) DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column returns incorrect information for BLOB CLOB data type

[ https://issues.apache.org/jira/browse/DERBY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490504 ] Saurabh Vyas commented on DERBY-2280: - Thanks alot Kathey Army. I 'll create a new patch with your inputs and

[jira] Commented: (DERBY-2280) DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column returns incorrect information for BLOB CLOB data type

[ https://issues.apache.org/jira/browse/DERBY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490222 ] Saurabh Vyas commented on DERBY-2280: - Hi Kathey, well a similar discussion on BLOB / CLOB for

[jira] Updated: (DERBY-2531) client returns different connection on s.getConnection() on a statement obtained from a ConnectionPoolDataSource or XADataSource than the original connection.

[ https://issues.apache.org/jira/browse/DERBY-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2531: Attachment: ConnPoolErr.java Attached a repro for this issue. Did a comparison on object created

[jira] Commented: (DERBY-2280) DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column returns incorrect information for BLOB CLOB data type

[ https://issues.apache.org/jira/browse/DERBY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480732 ] Saurabh Vyas commented on DERBY-2280: - When I ran tests on this the jdbcsuite runs fine (JUnit), but a quick

[jira] Commented: (DERBY-2445) Function VARCHAR truncates the results at 15 characters

[ https://issues.apache.org/jira/browse/DERBY-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_1248 ] Saurabh Vyas commented on DERBY-2445: - Hi Ephemeris, Can you please provide more details about which version of

[jira] Commented: (DERBY-2445) Function VARCHAR truncates the results at 15 characters

[ https://issues.apache.org/jira/browse/DERBY-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480021 ] Saurabh Vyas commented on DERBY-2445: - Hi Ephemeris, Well Derby-1132 which addresses truncation problem is

[jira] Updated: (DERBY-2262) DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types

[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2262: Attachment: Derby-2262_v2.diff Thanks Krisitan for looking at the patch your valuable comments.

[jira] Updated: (DERBY-2405) Remove @author tags from the source files

[ https://issues.apache.org/jira/browse/DERBY-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2405: Attachment: Derby-2405_v2.stat Derby-2405_v2.diff Thanks Kristian for your

[jira] Updated: (DERBY-2405) Remove @author tags from the source files

[ https://issues.apache.org/jira/browse/DERBY-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2405: Derby Info: [Patch Available] Again setting patch-available flag as the comments are incorporated

[jira] Updated: (DERBY-2405) Remove @author tags from the source files

[ https://issues.apache.org/jira/browse/DERBY-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2405: Attachment: Derby-2405_v3.stat Derby-2405_v3.diff Thanks a ton Kristian!!!

[jira] Closed: (DERBY-2405) Remove @author tags from the source files

[ https://issues.apache.org/jira/browse/DERBY-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas closed DERBY-2405. --- Thanks Kristian for committing this. Checked and verified it closing this issue. Remove @author

[jira] Created: (DERBY-2405) Remove @author tags from the source files

Remove @author tags from the source files - Key: DERBY-2405 URL: https://issues.apache.org/jira/browse/DERBY-2405 Project: Derby Issue Type: Task Reporter: Saurabh Vyas Assigned

[jira] Updated: (DERBY-2405) Remove @author tags from the source files

[ https://issues.apache.org/jira/browse/DERBY-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2405: Attachment: Derby-2405_v1.stat Derby-2405_v1.diff Remove @author tags from the

[jira] Updated: (DERBY-2405) Remove @author tags from the source files

[ https://issues.apache.org/jira/browse/DERBY-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2405: Derby Info: [Patch Available] Remove @author tags from the source files

[jira] Commented: (DERBY-2371) Setting a default value for a VARCHAR column fails when column contains data

[ https://issues.apache.org/jira/browse/DERBY-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475820 ] Saurabh Vyas commented on DERBY-2371: - Hi Bryan, I did some quick tests on your patch it works perfectly fine.

[jira] Commented: (DERBY-2307) DatabaseMetaData.getTypeInfo nullability is incorrect for columns 1,7 and 9

[ https://issues.apache.org/jira/browse/DERBY-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474959 ] Saurabh Vyas commented on DERBY-2307: - Well after a quick observation I found out that TYPE_NAME, NULLABLE,

[jira] Commented: (DERBY-2303) New master file for connectionJdbc20 needed

[ https://issues.apache.org/jira/browse/DERBY-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471223 ] Saurabh Vyas commented on DERBY-2303: - Currently the order of data type is correct in connectionJdbc20.out file.

[jira] Commented: (DERBY-2287) JDBC meta data for precision and size is inconsistent and does not match JDBC specifications.

[ https://issues.apache.org/jira/browse/DERBY-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471591 ] Saurabh Vyas commented on DERBY-2287: - I saw inconsistency for precision value in embedded network mode also.

[jira] Commented: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470904 ] Saurabh Vyas commented on DERBY-2243: - Thanks alot for modifying the assert condition in

[jira] Commented: (DERBY-2287) JDBC meta data for precision and size is inconsistent and does not match JDBC specifications.

[ https://issues.apache.org/jira/browse/DERBY-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470999 ] Saurabh Vyas commented on DERBY-2287: - After some investigation I found that getDigitPrecision() method in

[jira] Commented: (DERBY-2303) New master file for connectionJdbc20 needed

[ https://issues.apache.org/jira/browse/DERBY-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471078 ] Saurabh Vyas commented on DERBY-2303: - Well this is my mistake, I had modified the metadata.properties file and

[jira] Assigned: (DERBY-2303) New master file for connectionJdbc20 needed

[ https://issues.apache.org/jira/browse/DERBY-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas reassigned DERBY-2303: --- Assignee: Saurabh Vyas New master file for connectionJdbc20 needed

[jira] Commented: (DERBY-2287) JDBC meta data for precision and size is inconsistent and does not match JDBC specifications.

[ https://issues.apache.org/jira/browse/DERBY-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471191 ] Saurabh Vyas commented on DERBY-2287: - Thanks Dag Dan for your inputs. The inconsistency lies in the different

[jira] Updated: (DERBY-2289) Add jdk 1.6 support to jdbcapi tests.

[ https://issues.apache.org/jira/browse/DERBY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2289: Attachment: Derby-2289_v1.stat Derby-2289_v1.diff Modified build.xml in jdbcapi

[jira] Updated: (DERBY-2289) Add jdk 1.6 support to jdbcapi tests.

[ https://issues.apache.org/jira/browse/DERBY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2289: Derby Info: [Patch Available] Dan I tried your approach also now, that works fine as SQLXML

[jira] Commented: (DERBY-2289) Add jdk 1.6 support to jdbcapi tests.

[ https://issues.apache.org/jira/browse/DERBY-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470599 ] Saurabh Vyas commented on DERBY-2289: - Thanks Dan for this info. I 'll modify the test to use constant from

[jira] Updated: (DERBY-2258) DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.

[ https://issues.apache.org/jira/browse/DERBY-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2258: Attachment: Derby-2258_v3.stat Derby-2258_v3.diff Incorporated all the changes

[jira] Commented: (DERBY-2259) DatabaseMetaData.getTypeInfo() SEARCHABLE column returns incorrect information for types that cannot be searched.

[ https://issues.apache.org/jira/browse/DERBY-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470630 ] Saurabh Vyas commented on DERBY-2259: - Patch for Derby-2258 implements the modification required. This involves

[jira] Commented: (DERBY-2260) DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA

[ https://issues.apache.org/jira/browse/DERBY-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470632 ] Saurabh Vyas commented on DERBY-2260: - This correction in the PRECISION values requires change in

[jira] Commented: (DERBY-2260) DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA

[ https://issues.apache.org/jira/browse/DERBY-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470633 ] Saurabh Vyas commented on DERBY-2260: - I have a question regarding assertFalse(rs.wasNull()) in

[jira] Commented: (DERBY-2260) DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA

[ https://issues.apache.org/jira/browse/DERBY-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470667 ] Saurabh Vyas commented on DERBY-2260: - Thanks again. Added the check for XML data type that it can have NULL

[jira] Updated: (DERBY-2258) DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.

[ https://issues.apache.org/jira/browse/DERBY-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2258: Attachment: Derby-2258_v4.diff Modified the assert case for XML data type in

[jira] Resolved: (DERBY-2258) DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.

[ https://issues.apache.org/jira/browse/DERBY-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas resolved DERBY-2258. - Resolution: Fixed Thanks Dan. I 'll work on DERBY-2245 also and try to provide a final patch

[jira] Resolved: (DERBY-2259) DatabaseMetaData.getTypeInfo() SEARCHABLE column returns incorrect information for types that cannot be searched.

[ https://issues.apache.org/jira/browse/DERBY-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas resolved DERBY-2259. - Resolution: Fixed DatabaseMetaData.getTypeInfo() SEARCHABLE column returns incorrect

[jira] Resolved: (DERBY-2260) DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA

[ https://issues.apache.org/jira/browse/DERBY-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas resolved DERBY-2260. - Resolution: Fixed DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR

[jira] Resolved: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas resolved DERBY-2243. - Resolution: Fixed DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded,

[jira] Resolved: (DERBY-2244) DatabaseMetaData.supportsExpressionsInOrderBy() returns false

[ https://issues.apache.org/jira/browse/DERBY-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas resolved DERBY-2244. - Resolution: Fixed DatabaseMetaData.supportsExpressionsInOrderBy() returns false

[jira] Updated: (DERBY-2262) DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types

[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2262: Attachment: Derby-2262_v1.stat Derby-2262_v1.diff Corrected the Max Scale for

[jira] Updated: (DERBY-2262) DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types

[ https://issues.apache.org/jira/browse/DERBY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2262: Derby Info: [Patch Available] DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value

[jira] Created: (DERBY-2289) Add jdk 1.6 support to jdbcapi tests.

Add jdk 1.6 support to jdbcapi tests. - Key: DERBY-2289 URL: https://issues.apache.org/jira/browse/DERBY-2289 Project: Derby Issue Type: Improvement Components: JDBC Reporter:

[jira] Commented: (DERBY-2259) DatabaseMetaData.getTypeInfo() SEARCHABLE column returns incorrect information for types that cannot be searched.

[ https://issues.apache.org/jira/browse/DERBY-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468990 ] Saurabh Vyas commented on DERBY-2259: - Thanks Knut, I 'll modify the patch accordingly (along with the changes

[jira] Created: (DERBY-2280) DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column returns incorrect information for BLOB CLOB data type

DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column returns incorrect information for BLOB CLOB data type --- Key: DERBY-2280

[jira] Updated: (DERBY-2280) DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column returns incorrect information for BLOB CLOB data type

[ https://issues.apache.org/jira/browse/DERBY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2280: Attachment: Derby-2280.stat Derby-2280.diff Modified the value of

[jira] Updated: (DERBY-2280) DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column returns incorrect information for BLOB CLOB data type

[ https://issues.apache.org/jira/browse/DERBY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2280: Derby Info: [Patch Available] DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and

[jira] Updated: (DERBY-2258) DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.

[ https://issues.apache.org/jira/browse/DERBY-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2258: Attachment: Derby-2258.stat Derby-2258.diff After some investigations I found out

[jira] Updated: (DERBY-2258) DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.

[ https://issues.apache.org/jira/browse/DERBY-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2258: Derby Info: [Patch Available] DatabaseMetaData.getTypeInfo() does not list supported Derby SQL

[jira] Commented: (DERBY-2258) DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.

[ https://issues.apache.org/jira/browse/DERBY-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468608 ] Saurabh Vyas commented on DERBY-2258: - Modified the test output files also as datatype which are not supported

[jira] Updated: (DERBY-2258) DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.

[ https://issues.apache.org/jira/browse/DERBY-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2258: Attachment: Derby-2258_v2.diff Thanks Knut, A B Dan for your valuable comments. I had modified

[jira] Commented: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468256 ] Saurabh Vyas commented on DERBY-2243: - Thanks a lot Dan. I had files for ICLA now. Apart I had verified for this

[jira] Assigned: (DERBY-2258) DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.

[ https://issues.apache.org/jira/browse/DERBY-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas reassigned DERBY-2258: --- Assignee: Saurabh Vyas DatabaseMetaData.getTypeInfo() does not list supported Derby SQL

[jira] Assigned: (DERBY-2260) DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA

[ https://issues.apache.org/jira/browse/DERBY-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas reassigned DERBY-2260: --- Assignee: Saurabh Vyas DatabaseMetaData.getTypeInfo() returns incorrect precision for

[jira] Assigned: (DERBY-2259) DatabaseMetaData.getTypeInfo() SEARCHABLE column returns incorrect information for types that cannot be searched.

[ https://issues.apache.org/jira/browse/DERBY-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas reassigned DERBY-2259: --- Assignee: Saurabh Vyas DatabaseMetaData.getTypeInfo() SEARCHABLE column returns incorrect

[jira] Commented: (DERBY-2244) DatabaseMetaData.supportsExpressionsInOrderBy() returns false

[ https://issues.apache.org/jira/browse/DERBY-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466953 ] Saurabh Vyas commented on DERBY-2244: - This issue is addressed by the patch for DERBY-2243

[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

[ https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466994 ] Saurabh Vyas commented on DERBY-2017: - Thanks Kristian for bringing this issue to attention and another round of

[jira] Assigned: (DERBY-2245) DatabaseMetaData.getSQLKeywords() contains words that are not keywords in Derby.

[ https://issues.apache.org/jira/browse/DERBY-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas reassigned DERBY-2245: --- Assignee: Saurabh Vyas DatabaseMetaData.getSQLKeywords() contains words that are not

[jira] Commented: (DERBY-2245) DatabaseMetaData.getSQLKeywords() contains words that are not keywords in Derby.

[ https://issues.apache.org/jira/browse/DERBY-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_1245 ] Saurabh Vyas commented on DERBY-2245: - I am interested in working on this. EmbedDatabaseMetaData implements

[jira] Commented: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466112 ] Saurabh Vyas commented on DERBY-2243: - I looked into the code and found that

[jira] Updated: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2243: Attachment: Derby-2243_v1.stat Derby-2243_v1.diff

[jira] Updated: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2243: Derby Info: [Patch Available] Fix Version/s: 10.3.0.0 Modifying the return type for methods

[jira] Commented: (DERBY-2244) DatabaseMetaData.supportsExpressionsInOrderBy() returns false

[ https://issues.apache.org/jira/browse/DERBY-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466120 ] Saurabh Vyas commented on DERBY-2244: - Modifying the return type for methods supportsExpressionsInOrderBy() in

[jira] Commented: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466128 ] Saurabh Vyas commented on DERBY-2243: - My apologies on this and thanks Dan for correcting me. Well what I was

[jira] Updated: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas updated DERBY-2243: Attachment: Derby-2243_v2.stat Derby-2243_v2.diff

[jira] Commented: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466212 ] Saurabh Vyas commented on DERBY-2243: - Thanks Dan for your comments and guiding me for best practices (i.e.

[jira] Assigned: (DERBY-2243) DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver

[ https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saurabh Vyas reassigned DERBY-2243: --- Assignee: Saurabh Vyas DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for

[jira] Commented: (DERBY-1963) Routine parameter names displayed by dblook are not escaped.

[ https://issues.apache.org/jira/browse/DERBY-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463865 ] Saurabh Vyas commented on DERBY-1963: - I tried reproducing this, but while using the dblook output to create the

[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

[ http://issues.apache.org/jira/browse/DERBY-2017?page=all ] Saurabh Vyas reassigned DERBY-2017: --- Assignee: Saurabh Vyas Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length

[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

[ http://issues.apache.org/jira/browse/DERBY-2017?page=all ] Saurabh Vyas updated DERBY-2017: Attachment: Derby_2017_v1.diff Derby_2017_v1.stat When an error occurs, rolling back the transaction in network mode so as the database

[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

[ http://issues.apache.org/jira/browse/DERBY-2017?page=all ] Saurabh Vyas updated DERBY-2017: Fix Version/s: 10.3.0.0 Derby Info: [Patch Available] Client driver can insert and commit partial data when a LOB stream throws IOException or does

[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

[ http://issues.apache.org/jira/browse/DERBY-2017?page=all ] Saurabh Vyas updated DERBY-2017: Fix Version/s: 10.2.2.0 Adding fixed version to 10.2.2 also Client driver can insert and commit partial data when a LOB stream throws IOException or does

[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

[ http://issues.apache.org/jira/browse/DERBY-2017?page=comments#action_12456523 ] Saurabh Vyas commented on DERBY-2017: - Well with this approach, the two configurations will behave differently. In embedded mode, in case of error, only the

[jira] Updated: (DERBY-1132) Truncation Error with Concat

[ http://issues.apache.org/jira/browse/DERBY-1132?page=all ] Saurabh Vyas updated DERBY-1132: Attachment: derby_1132_v1.diff derby_1132_v1.stat The Char Varchar functions were not handled separately to assign to length for the target

[jira] Updated: (DERBY-1132) Truncation Error with Concat

[ http://issues.apache.org/jira/browse/DERBY-1132?page=all ] Saurabh Vyas updated DERBY-1132: Derby Info: [Patch Available] Truncation Error with Concat Key: DERBY-1132 URL:

[jira] Updated: (DERBY-1132) Truncation Error with Concat

[ http://issues.apache.org/jira/browse/DERBY-1132?page=all ] Saurabh Vyas updated DERBY-1132: Fix Version/s: 10.3.0.0 Truncation Error with Concat Key: DERBY-1132 URL:

[jira] Assigned: (DERBY-1132) Truncation Error with Concat

[ http://issues.apache.org/jira/browse/DERBY-1132?page=all ] Saurabh Vyas reassigned DERBY-1132: --- Assignee: Saurabh Vyas Truncation Error with Concat Key: DERBY-1132 URL:

[jira] Commented: (DERBY-1645) ALTER TABLE ... SET INCREMENT BY X... Turns off the Generated By Default identity column constraint

[ http://issues.apache.org/jira/browse/DERBY-1645?page=comments#action_12443455 ] Saurabh Vyas commented on DERBY-1645: - I further investigated on this and following is the summary for that : - when alter table is executed,

[jira] Commented: (DERBY-1645) ALTER TABLE ... SET INCREMENT BY X... Turns off the Generated By Default identity column constraint

[ http://issues.apache.org/jira/browse/DERBY-1645?page=comments#action_12438080 ] Saurabh Vyas commented on DERBY-1645: - I have investigated on this issue and found out that when we create a table with 'GENERATED BY DEFAULT AS IDENTITY' ,

[jira] Commented: (DERBY-1763) Using RTRIM(LTRIM(col)) and group by col gives NPE

[ http://issues.apache.org/jira/browse/DERBY-1763?page=comments#action_12434080 ] Saurabh Vyas commented on DERBY-1763: - I tried to simulate the same scenario on Derby-10.2 and it works fine here with no excption/assert. ij version 10.2