| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2725) If all the operands involved in collation operation have a collation derivation of NONE, then Derby should throw an exception for that as per the SQL standards. |
Fri, 06 Jul, 11:19 |
| Mamta A. Satoor (JIRA) |
[jira] Closed: (DERBY-2725) If all the operands involved in collation operation have a collation derivation of NONE, then Derby should throw an exception for that as per the SQL standards. |
Fri, 06 Jul, 11:21 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2909) TernaryOperatorNode does not check the collation type of it's operands when implementing TRIM, LOCATE functions. |
Mon, 09 Jul, 16:02 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2910) SimpleStringOperatorNode in it's bindExpression method generates a character string CAST if required but does not set the correct collation. |
Mon, 09 Jul, 16:41 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2909) TernaryOperatorNode does not check the collation type of it's operands when implementing TRIM, LOCATE functions. |
Mon, 09 Jul, 17:11 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2909) TernaryOperatorNode does not check the collation type of it's operands when implementing TRIM, LOCATE functions. |
Mon, 09 Jul, 18:28 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2909) TernaryOperatorNode does not check the collation type of it's operands when implementing TRIM, LOCATE functions. |
Mon, 09 Jul, 23:42 |
| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2909) TernaryOperatorNode does not check the collation type of it's operands when implementing TRIM, LOCATE functions. |
Mon, 09 Jul, 23:42 |
| Mamta A. Satoor (JIRA) |
[jira] Closed: (DERBY-2909) TernaryOperatorNode does not check the collation type of it's operands when implementing TRIM, LOCATE functions. |
Mon, 09 Jul, 23:44 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation |
Mon, 09 Jul, 23:58 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2919) Alter table .. Add .. Primary Key fails with Column not found when columnName contains localized characters - w/a available |
Wed, 11 Jul, 05:40 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2919) Alter table .. Add .. Primary Key fails with Column not found when columnName contains localized characters - w/a available |
Wed, 11 Jul, 05:46 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2894) calling DatabaseMetaData.getColumns() with % for matching column character in a territory based collated db does not work in 1.4.2 jvms |
Wed, 11 Jul, 06:19 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Wed, 11 Jul, 18:24 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Wed, 11 Jul, 22:13 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Thu, 12 Jul, 05:59 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Thu, 12 Jul, 16:20 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Thu, 12 Jul, 16:45 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Thu, 12 Jul, 18:59 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Tue, 17 Jul, 18:07 |
| Mamta A. Satoor (JIRA) |
[jira] Created: (DERBY-2946) In soft upgrade mode, the metadata queries do not get compiled in SYS schema. This will cause problems in future releases of Derby. |
Tue, 17 Jul, 18:46 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Wed, 18 Jul, 00:34 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2940) CollationTest fail after hard upgrade from 10.2 |
Wed, 18 Jul, 15:49 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Wed, 18 Jul, 17:08 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2940) CollationTest fail after hard upgrade from 10.2 |
Wed, 18 Jul, 18:18 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2940) CollationTest fail after hard upgrade from 10.2 |
Wed, 18 Jul, 18:34 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed. |
Wed, 18 Jul, 21:48 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2950) BatchUpdateTest.testMinimalDDLInBatch Fails when run with collation with exception: java.sql.SQLException: Operand of LIKE predicate with type VARCHAR(128) and collation UCS_BASIC is not compatable with LIKE pattern operand with type CHAR(4) and collation |
Wed, 18 Jul, 21:50 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2950) BatchUpdateTest.testMinimalDDLInBatch Fails when run with collation with exception: java.sql.SQLException: Operand of LIKE predicate with type VARCHAR(128) and collation UCS_BASIC is not compatable with LIKE pattern operand with type CHAR(4) and collation |
Thu, 19 Jul, 05:52 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2950) BatchUpdateTest.testMinimalDDLInBatch Fails when run with collation with exception: java.sql.SQLException: Operand of LIKE predicate with type VARCHAR(128) and collation UCS_BASIC is not compatable with LIKE pattern operand with type CHAR(4) and collation |
Thu, 19 Jul, 05:52 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2956) With a collated database USER cannot be used in query against user tables without cast |
Thu, 19 Jul, 16:05 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2950) BatchUpdateTest.testMinimalDDLInBatch Fails when run with collation with exception: java.sql.SQLException: Operand of LIKE predicate with type VARCHAR(128) and collation UCS_BASIC is not compatable with LIKE pattern operand with type CHAR(4) and collation |
Thu, 19 Jul, 16:26 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2656) Run suites.All against a collated database |
Thu, 19 Jul, 17:13 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2951) BatchUpdateTest.testAssociatedParams test fails with collation with exception: Java exception: 'ASSERT FAILED type of inserted column[0] = org.apache.derby.iapi.types.CollatorSQLChartype of template column[0] = org.apache.derby.iapi.types.SQLChar: |
Thu, 19 Jul, 17:13 |
| Mamta A. Satoor (JIRA) |
[jira] Created: (DERBY-2959) create table ... as select ... from systemtable with no data fails even when there is no character string type involved. This happens in a territory based database |
Thu, 19 Jul, 17:55 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2959) create table ... as select ... from systemtable with no data fails even when there is no character string type involved. This happens in a territory based database |
Thu, 19 Jul, 18:03 |
| Mamta A. Satoor (JIRA) |
[jira] Updated: (DERBY-2656) Run suites.All against a collated database |
Thu, 19 Jul, 18:05 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2656) Run suites.All against a collated database |
Thu, 19 Jul, 18:07 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2959) create table ... as select ... from systemtable with no data fails even when there is no character string type involved. This happens in a territory based database |
Thu, 19 Jul, 18:16 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2951) BatchUpdateTest.testAssociatedParams test fails with collation with exception: Java exception: 'ASSERT FAILED type of inserted column[0] = org.apache.derby.iapi.types.CollatorSQLChartype of template column[0] = org.apache.derby.iapi.types.SQLChar: |
Thu, 19 Jul, 18:18 |
| Mamta A. Satoor (JIRA) |
[jira] Closed: (DERBY-2959) create table ... as select ... from systemtable with no data fails even when there is no character string type involved. This happens in a territory based database |
Fri, 20 Jul, 05:50 |
| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2959) create table ... as select ... from systemtable with no data fails even when there is no character string type involved. This happens in a territory based database |
Fri, 20 Jul, 05:50 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2955) ERROR 42ZA2 creating table with check constraint with literal comparison |
Fri, 20 Jul, 06:32 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2955) ERROR 42ZA2 creating table with check constraint with literal comparison |
Fri, 20 Jul, 06:45 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2952) create table from values clause causes error: ERROR 42ZA3: The table will have collation type UCS_BASIC which is different than the collation of the schema TERRITORY_BASED |
Fri, 20 Jul, 06:55 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2952) create table from values clause causes error: ERROR 42ZA3: The table will have collation type UCS_BASIC which is different than the collation of the schema TERRITORY_BASED |
Fri, 20 Jul, 06:57 |
| Mamta A. Satoor (JIRA) |
[jira] Updated: (DERBY-2952) create table from values clause causes error: ERROR 42ZA3: The table will have collation type UCS_BASIC which is different than the collation of the schema TERRITORY_BASED |
Fri, 20 Jul, 06:59 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2952) create table from values clause causes error: ERROR 42ZA3: The table will have collation type UCS_BASIC which is different than the collation of the schema TERRITORY_BASED |
Fri, 20 Jul, 07:01 |
| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2952) create table from values clause causes error: ERROR 42ZA3: The table will have collation type UCS_BASIC which is different than the collation of the schema TERRITORY_BASED |
Fri, 20 Jul, 07:01 |
| Mamta A. Satoor (JIRA) |
[jira] Reopened: (DERBY-2952) create table from values clause causes error: ERROR 42ZA3: The table will have collation type UCS_BASIC which is different than the collation of the schema TERRITORY_BASED |
Fri, 20 Jul, 07:01 |
| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2952) create table from values clause causes error: ERROR 42ZA3: The table will have collation type UCS_BASIC which is different than the collation of the schema TERRITORY_BASED |
Fri, 20 Jul, 07:03 |
| Mamta A. Satoor (JIRA) |
[jira] Closed: (DERBY-2952) create table from values clause causes error: ERROR 42ZA3: The table will have collation type UCS_BASIC which is different than the collation of the schema TERRITORY_BASED |
Fri, 20 Jul, 07:05 |
| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2955) ERROR 42ZA2 creating table with check constraint with literal comparison |
Fri, 20 Jul, 07:42 |
| Mamta A. Satoor (JIRA) |
[jira] Closed: (DERBY-2955) ERROR 42ZA2 creating table with check constraint with literal comparison |
Fri, 20 Jul, 07:42 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2960) Group by substr() on collated database causes ERROR XJ001: Java exception: 'ASSERT FAILED col1.getClass() (class org.apache.derby.iapi.types.SQLVarchar) expected to be the same as col2.getClass() (class org.apache.derby.iapi.types.CollatorSQLVarchar): |
Fri, 20 Jul, 08:39 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2960) Group by substr() on collated database causes ERROR XJ001: Java exception: 'ASSERT FAILED col1.getClass() (class org.apache.derby.iapi.types.SQLVarchar) expected to be the same as col2.getClass() (class org.apache.derby.iapi.types.CollatorSQLVarchar): |
Fri, 20 Jul, 08:39 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2960) Group by substr() on collated database causes ERROR XJ001: Java exception: 'ASSERT FAILED col1.getClass() (class org.apache.derby.iapi.types.SQLVarchar) expected to be the same as col2.getClass() (class org.apache.derby.iapi.types.CollatorSQLVarchar): |
Fri, 20 Jul, 16:59 |
| Mamta A. Satoor (JIRA) |
[jira] Closed: (DERBY-2960) Group by substr() on collated database causes ERROR XJ001: Java exception: 'ASSERT FAILED col1.getClass() (class org.apache.derby.iapi.types.SQLVarchar) expected to be the same as col2.getClass() (class org.apache.derby.iapi.types.CollatorSQLVarchar): |
Fri, 20 Jul, 16:59 |
| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2960) Group by substr() on collated database causes ERROR XJ001: Java exception: 'ASSERT FAILED col1.getClass() (class org.apache.derby.iapi.types.SQLVarchar) expected to be the same as col2.getClass() (class org.apache.derby.iapi.types.CollatorSQLVarchar): |
Fri, 20 Jul, 16:59 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2959) create table ... as select ... from systemtable with no data fails even when there is no character string type involved. This happens in a territory based database |
Mon, 23 Jul, 17:07 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2966) rs.moveToInsertRow() causes loss of connection with TERRITORY_BASED collation. |
Tue, 24 Jul, 17:44 |
| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2966) rs.moveToInsertRow() causes loss of connection with TERRITORY_BASED collation. |
Tue, 24 Jul, 17:46 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2966) rs.moveToInsertRow() causes loss of connection with TERRITORY_BASED collation. |
Tue, 24 Jul, 17:46 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2973) With collation TERRITORY_BASED, insert into table after changing type of column causes assert failure and loss of connection |
Fri, 27 Jul, 15:55 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2973) With collation TERRITORY_BASED, insert into table after changing type of column causes assert failure and loss of connection |
Fri, 27 Jul, 15:55 |
| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2973) With collation TERRITORY_BASED, insert into table after changing type of column causes assert failure and loss of connection |
Fri, 27 Jul, 16:45 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation |
Tue, 31 Jul, 20:30 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation |
Tue, 31 Jul, 20:52 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation |
Tue, 31 Jul, 20:54 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation |
Wed, 01 Aug, 05:45 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation |
Wed, 01 Aug, 05:49 |
| Mamta A. Satoor (JIRA) |
[jira] Assigned: (DERBY-2964) ASSERT FAILED type of inserted column[0] = org.apache.derby.iapi.types.SQLVarchar type of template column[0] = org.apache.derby.iapi.types.CollatorSQLVarchar when inserting row into table that has been modified with unique constraint |
Wed, 01 Aug, 06:08 |
| Mamta A. Satoor (JIRA) |
[jira] Commented: (DERBY-2964) ASSERT FAILED type of inserted column[0] = org.apache.derby.iapi.types.SQLVarchar type of template column[0] = org.apache.derby.iapi.types.CollatorSQLVarchar when inserting row into table that has been modified with unique constraint |
Wed, 01 Aug, 06:14 |
| Mamta A. Satoor (JIRA) |
[jira] Resolved: (DERBY-2964) ASSERT FAILED type of inserted column[0] = org.apache.derby.iapi.types.SQLVarchar type of template column[0] = org.apache.derby.iapi.types.CollatorSQLVarchar when inserting row into table that has been modified with unique constraint |
Wed, 01 Aug, 06:16 |
| Mamta Satoor |
Re: Regarding DERBY-2750 |
Mon, 02 Jul, 17:09 |
| Mamta Satoor |
Re: Regarding DERBY-2750 |
Mon, 02 Jul, 17:34 |
| Mamta Satoor |
Re: 10.3 updates to SQLvsDerbyFeatures |
Tue, 03 Jul, 16:30 |
| Mamta Satoor |
Re: 10.3 updates to SQLvsDerbyFeatures |
Wed, 04 Jul, 23:27 |
| Mamta Satoor |
Documentation for SYSTABLES in reference manual does not mention 'A' for synonym type in TABLETYPE column |
Wed, 18 Jul, 02:28 |
| Mamta Satoor |
Re: again, another 10.3.1. release candidate? |
Wed, 18 Jul, 21:44 |
| Mamta Satoor |
Re: Single character does not match high value unicode character with collation TERRITORY_BASED. Is this a bug |
Fri, 20 Jul, 18:52 |
| Mamta Satoor |
Re: Single character does not match high value unicode character with collation TERRITORY_BASED. Is this a bug |
Mon, 23 Jul, 16:47 |
| Mamta Satoor |
Re: Should we have dynamic like optimization with TERRITORY_BASED collation |
Mon, 23 Jul, 17:45 |
| Mamta Satoor |
Re: svn commit: r561494 - in /db/derby/code/trunk/java/engine/org/apache/derby: iapi/types/DataTypeDescriptor.java impl/sql/compile/LikeEscapeOperatorNode.java |
Tue, 31 Jul, 20:38 |
| Mamta Satoor |
Re: svn commit: r561514 - /db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/DataTypeDescriptor.java |
Wed, 01 Aug, 03:48 |
| Manish Khettry |
Re: DERBY-581 and OLAP operations |
Wed, 18 Jul, 21:18 |
| Manish Khettry (JIRA) |
[jira] Updated: (DERBY-2689) Deadlock with GenericPreparedStatement |
Mon, 02 Jul, 03:25 |
| Manish Khettry (JIRA) |
[jira] Updated: (DERBY-2689) Deadlock with GenericPreparedStatement |
Mon, 02 Jul, 16:45 |
| Manish Khettry (JIRA) |
[jira] Commented: (DERBY-2689) Deadlock with GenericPreparedStatement |
Tue, 03 Jul, 04:31 |
| Manish Khettry (JIRA) |
[jira] Updated: (DERBY-2689) Deadlock with GenericPreparedStatement |
Tue, 03 Jul, 17:45 |
| Manish Khettry (JIRA) |
[jira] Updated: (DERBY-2689) Deadlock with GenericPreparedStatement |
Tue, 03 Jul, 17:47 |
| Manjula Kutty |
Optimization test result |
Mon, 09 Jul, 20:17 |
| Manjula Kutty |
Re: Optimization test result |
Tue, 10 Jul, 16:57 |
| Manjula Kutty |
Re: again, another 10.3.1. release candidate? |
Wed, 18 Jul, 21:42 |
| Manjula Kutty |
About DERBY-2963 |
Fri, 20 Jul, 19:56 |
| Manjula Kutty |
Re: [jira] Commented: (DERBY-2963) AccessControlException: Access denied java.net.SocketPermission <client ip> accept,resolve |
Wed, 25 Jul, 19:13 |
| Manjula Kutty |
Re: starting network server with classes... |
Fri, 27 Jul, 17:50 |
| Manjula Kutty |
Re: Unsubscribe? |
Sat, 28 Jul, 00:04 |
| Manjula Kutty |
Eclipse plugin |
Mon, 30 Jul, 22:09 |
| Manjula Kutty (JIRA) |
[jira] Commented: (DERBY-2874) NetworkServer not accepting connections with default security manager on Ipv6 machines |
Tue, 03 Jul, 00:19 |