Home » Eclipse Projects » DTP » Derby territory based databases
| Derby territory based databases [message #45361] |
Sat, 14 June 2008 15:30  |
Eclipse User |
|
|
|
Originally posted by: whistle.worldonline.nl
Hi,
I'm trying to use the latest RC3 packages with Derby databases that use
territory-based collation, but no database properties in any schema
(tables, stored procedures etc.) are viewable.
This used to be a known problem with the Derby-tools itself. The error
message that Derby returns is the following:
---
Failed Statement is: SELECT TABLENAME AS TABLE_NAME, TABLETYPE AS
TABLE_TYPE FROM SYS.SYSTABLES A,SYS.SYSSCHEMAS B WHERE
A.SCHEMAID=B.SCHEMAID AND B.SCHEMANAME='AZLOGISTICS' AND ( TABLETYPE='A'
OR TABLETYPE='T' OR TABLETYPE='S' OR TABLETYPE='V' )
ERROR 42818: Comparisons between 'VARCHAR (UCS_BASIC)' and 'CHAR
(TERRITORY_BASED)' are not supported. Types must be comparable. String
types must also have matching collation. If collation does not match, a
possible solution is to cast operands to force them to the default
collation (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename
AS VARCHAR(128)) = 'T1')
/---
This information is somewhat misleading. For regular comparisons, the
workaround suggested in the error message does apply, but for retrieving
database schema information, the workaround is as simple as executing a
'SET SCHEMA SYS;' statement on the connection before the 'SELECT
TABLENAME....'
This generally accounts for retrieving any database schema information.
For related information, please see the following URL:
https://issues.apache.org/jira/browse/DERBY-3458
I made a custom fix for this when using previous versions of DTP, but
that build process is so cumbersome, that I would be very pleased to see
this getting fixed before Ganymede gets released.
Regards,
Stephan van Loendersloot.
|
|
|
| Re: Derby territory based databases [message #45600 is a reply to message #45361] |
Wed, 18 June 2008 14:42  |
| Eclipse User |
|
|
|
Originally posted by: brianf.sybase.com
Hey Stephan...
Unfortunately we're at the end of the Ganymede time frame and past the
window for fixes for the 1.6 release. However... That doesn't mean that this
fix couldn't work into the 1.6.1 release which is slated for September.
Can you create a bugzilla entry for it and maybe attach a patch? If you've
been patching it in prior releases, you most likely have a patch that we
could review and apply for the maintenance release.
Sorry this has caused issues for you, but we'll see what we can do in 1.6.1.
--Fitz
"Stephan van Loendersloot" <whistle@worldonline.nl> wrote in message
news:g30o5v$jf2$1@build.eclipse.org...
> Hi,
>
> I'm trying to use the latest RC3 packages with Derby databases that use
> territory-based collation, but no database properties in any schema
> (tables, stored procedures etc.) are viewable.
>
> This used to be a known problem with the Derby-tools itself. The error
> message that Derby returns is the following:
>
> ---
>
> Failed Statement is: SELECT TABLENAME AS TABLE_NAME, TABLETYPE AS
> TABLE_TYPE FROM SYS.SYSTABLES A,SYS.SYSSCHEMAS B WHERE
> A.SCHEMAID=B.SCHEMAID AND B.SCHEMANAME='AZLOGISTICS' AND ( TABLETYPE='A'
> OR TABLETYPE='T' OR TABLETYPE='S' OR TABLETYPE='V' )
>
> ERROR 42818: Comparisons between 'VARCHAR (UCS_BASIC)' and 'CHAR
> (TERRITORY_BASED)' are not supported. Types must be comparable. String
> types must also have matching collation. If collation does not match, a
> possible solution is to cast operands to force them to the default
> collation (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename
> AS VARCHAR(128)) = 'T1')
>
> /---
>
> This information is somewhat misleading. For regular comparisons, the
> workaround suggested in the error message does apply, but for retrieving
> database schema information, the workaround is as simple as executing a
> 'SET SCHEMA SYS;' statement on the connection before the 'SELECT
> TABLENAME....'
>
> This generally accounts for retrieving any database schema information.
>
> For related information, please see the following URL:
>
> https://issues.apache.org/jira/browse/DERBY-3458
>
> I made a custom fix for this when using previous versions of DTP, but that
> build process is so cumbersome, that I would be very pleased to see this
> getting fixed before Ganymede gets released.
>
>
> Regards,
>
> Stephan van Loendersloot.
|
|
|
| Re: Derby territory based databases [message #45690 is a reply to message #45600] |
Thu, 19 June 2008 18:26 |
 Stephan van Loendersloot
Messages: 7
Registered: July 2009 |
Junior Member |
|
|
Hi Brian,
Thanks for your response, it hasn't caused me any problems so far, so no
worries ;-)
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=237834 for
this issue and will be looking into a creating a patch.
The last time I created a patch, I built the whole DTP package, with
some other minor changes (personal try-outs). That won't be neccessary
anymore, so I'll just update the derby-connectivity part, which should
be trivial.
Will be back soon.
Regards,
Stephan van Loendersloot.
Brian Fitzpatrick wrote:
> Hey Stephan...
>
> Unfortunately we're at the end of the Ganymede time frame and past the
> window for fixes for the 1.6 release. However... That doesn't mean that this
> fix couldn't work into the 1.6.1 release which is slated for September.
>
> Can you create a bugzilla entry for it and maybe attach a patch? If you've
> been patching it in prior releases, you most likely have a patch that we
> could review and apply for the maintenance release.
>
> Sorry this has caused issues for you, but we'll see what we can do in 1.6.1.
>
> --Fitz
>
> "Stephan van Loendersloot" <whistle@worldonline.nl> wrote in message
> news:g30o5v$jf2$1@build.eclipse.org...
>> Hi,
>>
>> I'm trying to use the latest RC3 packages with Derby databases that use
>> territory-based collation, but no database properties in any schema
>> (tables, stored procedures etc.) are viewable.
>>
>> This used to be a known problem with the Derby-tools itself. The error
>> message that Derby returns is the following:
>>
>> ---
>>
>> Failed Statement is: SELECT TABLENAME AS TABLE_NAME, TABLETYPE AS
>> TABLE_TYPE FROM SYS.SYSTABLES A,SYS.SYSSCHEMAS B WHERE
>> A.SCHEMAID=B.SCHEMAID AND B.SCHEMANAME='AZLOGISTICS' AND ( TABLETYPE='A'
>> OR TABLETYPE='T' OR TABLETYPE='S' OR TABLETYPE='V' )
>>
>> ERROR 42818: Comparisons between 'VARCHAR (UCS_BASIC)' and 'CHAR
>> (TERRITORY_BASED)' are not supported. Types must be comparable. String
>> types must also have matching collation. If collation does not match, a
>> possible solution is to cast operands to force them to the default
>> collation (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename
>> AS VARCHAR(128)) = 'T1')
>>
>> /---
>>
>> This information is somewhat misleading. For regular comparisons, the
>> workaround suggested in the error message does apply, but for retrieving
>> database schema information, the workaround is as simple as executing a
>> 'SET SCHEMA SYS;' statement on the connection before the 'SELECT
>> TABLENAME....'
>>
>> This generally accounts for retrieving any database schema information.
>>
>> For related information, please see the following URL:
>>
>> https://issues.apache.org/jira/browse/DERBY-3458
>>
>> I made a custom fix for this when using previous versions of DTP, but that
>> build process is so cumbersome, that I would be very pleased to see this
>> getting fixed before Ganymede gets released.
>>
>>
>> Regards,
>>
>> Stephan van Loendersloot.
>
>
|
|
|
| Re: Derby territory based databases [message #591517 is a reply to message #45361] |
Wed, 18 June 2008 14:42 |
Brian Fitzpatrick
Messages: 500
Registered: July 2009 |
Senior Member |
|
|
Hey Stephan...
Unfortunately we're at the end of the Ganymede time frame and past the
window for fixes for the 1.6 release. However... That doesn't mean that this
fix couldn't work into the 1.6.1 release which is slated for September.
Can you create a bugzilla entry for it and maybe attach a patch? If you've
been patching it in prior releases, you most likely have a patch that we
could review and apply for the maintenance release.
Sorry this has caused issues for you, but we'll see what we can do in 1.6.1.
--Fitz
"Stephan van Loendersloot" <whistle@worldonline.nl> wrote in message
news:g30o5v$jf2$1@build.eclipse.org...
> Hi,
>
> I'm trying to use the latest RC3 packages with Derby databases that use
> territory-based collation, but no database properties in any schema
> (tables, stored procedures etc.) are viewable.
>
> This used to be a known problem with the Derby-tools itself. The error
> message that Derby returns is the following:
>
> ---
>
> Failed Statement is: SELECT TABLENAME AS TABLE_NAME, TABLETYPE AS
> TABLE_TYPE FROM SYS.SYSTABLES A,SYS.SYSSCHEMAS B WHERE
> A.SCHEMAID=B.SCHEMAID AND B.SCHEMANAME='AZLOGISTICS' AND ( TABLETYPE='A'
> OR TABLETYPE='T' OR TABLETYPE='S' OR TABLETYPE='V' )
>
> ERROR 42818: Comparisons between 'VARCHAR (UCS_BASIC)' and 'CHAR
> (TERRITORY_BASED)' are not supported. Types must be comparable. String
> types must also have matching collation. If collation does not match, a
> possible solution is to cast operands to force them to the default
> collation (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename
> AS VARCHAR(128)) = 'T1')
>
> /---
>
> This information is somewhat misleading. For regular comparisons, the
> workaround suggested in the error message does apply, but for retrieving
> database schema information, the workaround is as simple as executing a
> 'SET SCHEMA SYS;' statement on the connection before the 'SELECT
> TABLENAME....'
>
> This generally accounts for retrieving any database schema information.
>
> For related information, please see the following URL:
>
> https://issues.apache.org/jira/browse/DERBY-3458
>
> I made a custom fix for this when using previous versions of DTP, but that
> build process is so cumbersome, that I would be very pleased to see this
> getting fixed before Ganymede gets released.
>
>
> Regards,
>
> Stephan van Loendersloot.
|
|
|
| Re: Derby territory based databases [message #591548 is a reply to message #45600] |
Thu, 19 June 2008 18:26 |
Stephan van Loendersloot
Messages: 7
Registered: July 2009 |
Junior Member |
|
|
Hi Brian,
Thanks for your response, it hasn't caused me any problems so far, so no
worries ;-)
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=237834 for
this issue and will be looking into a creating a patch.
The last time I created a patch, I built the whole DTP package, with
some other minor changes (personal try-outs). That won't be neccessary
anymore, so I'll just update the derby-connectivity part, which should
be trivial.
Will be back soon.
Regards,
Stephan van Loendersloot.
Brian Fitzpatrick wrote:
> Hey Stephan...
>
> Unfortunately we're at the end of the Ganymede time frame and past the
> window for fixes for the 1.6 release. However... That doesn't mean that this
> fix couldn't work into the 1.6.1 release which is slated for September.
>
> Can you create a bugzilla entry for it and maybe attach a patch? If you've
> been patching it in prior releases, you most likely have a patch that we
> could review and apply for the maintenance release.
>
> Sorry this has caused issues for you, but we'll see what we can do in 1.6.1.
>
> --Fitz
>
> "Stephan van Loendersloot" <whistle@worldonline.nl> wrote in message
> news:g30o5v$jf2$1@build.eclipse.org...
>> Hi,
>>
>> I'm trying to use the latest RC3 packages with Derby databases that use
>> territory-based collation, but no database properties in any schema
>> (tables, stored procedures etc.) are viewable.
>>
>> This used to be a known problem with the Derby-tools itself. The error
>> message that Derby returns is the following:
>>
>> ---
>>
>> Failed Statement is: SELECT TABLENAME AS TABLE_NAME, TABLETYPE AS
>> TABLE_TYPE FROM SYS.SYSTABLES A,SYS.SYSSCHEMAS B WHERE
>> A.SCHEMAID=B.SCHEMAID AND B.SCHEMANAME='AZLOGISTICS' AND ( TABLETYPE='A'
>> OR TABLETYPE='T' OR TABLETYPE='S' OR TABLETYPE='V' )
>>
>> ERROR 42818: Comparisons between 'VARCHAR (UCS_BASIC)' and 'CHAR
>> (TERRITORY_BASED)' are not supported. Types must be comparable. String
>> types must also have matching collation. If collation does not match, a
>> possible solution is to cast operands to force them to the default
>> collation (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename
>> AS VARCHAR(128)) = 'T1')
>>
>> /---
>>
>> This information is somewhat misleading. For regular comparisons, the
>> workaround suggested in the error message does apply, but for retrieving
>> database schema information, the workaround is as simple as executing a
>> 'SET SCHEMA SYS;' statement on the connection before the 'SELECT
>> TABLENAME....'
>>
>> This generally accounts for retrieving any database schema information.
>>
>> For related information, please see the following URL:
>>
>> https://issues.apache.org/jira/browse/DERBY-3458
>>
>> I made a custom fix for this when using previous versions of DTP, but that
>> build process is so cumbersome, that I would be very pleased to see this
>> getting fixed before Ganymede gets released.
>>
>>
>> Regards,
>>
>> Stephan van Loendersloot.
>
>
|
|
|
Goto Forum:
Current Time: Tue Apr 16 04:33:02 GMT 2024
Powered by FUDForum. Page generated in 0.50820 seconds |
] 
Search
Help
Register
Login
Home
