dbTalk Databases Forums  

JOIN databases of different charsets

comp.databases.informix comp.databases.informix


Discuss JOIN databases of different charsets in the comp.databases.informix forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Kamenik, Aleksander
 
Posts: n/a

Default JOIN databases of different charsets - 03-23-2011 , 07:51 AM






Hi,

We several databases in informix, some are utf-8, others are iso-8859-1.

Is it possible to do a JOIN query from the two databases without getting a "database locale mismatch"?

I think the problem is ifx needs to compare data in different charsets internally for the JOIN, which is not possible. But maybe there's a way to force internal charset conversion for the JOIN even if it would result in slow queries.

We're planning on migrating more databases from ISO-8859 to UTF-8 and it would help immensely to be able to JOIN two databases of different charsets during the migration period.

Running Informix 11.70.UC1.

Regards,

Aleksander Kamenik
System Administrator
Krediidiinfo AS
an Experian Company
Phone: +372 665 9649
Email: aleksander (AT) krediidiinfo (DOT) ee

Reply With Quote
  #2  
Old   
Kamenik, Aleksander
 
Posts: n/a

Default RE: JOIN databases of different charsets - 03-24-2011 , 03:10 AM






Quote:
From: Fernando Nunes [mailto:domusonline (AT) gmail (DOT) com]

I believe Ian is missing the point. The issue is not unloading data and
load it into a different locale.
Apparently the issue is that the applications require distributed
queries between two (or more) databases with different locales.

You are correct.

Quote:
I believe this could be achieved with an undocumented variable setup in
the environment.
Check this article for further information:

https://www.ibm.com/developerworks/m.../gbowerman/ent
ry/trouble_with_locales?lang=en

Now... The idea behind this variable was not allowing this. But the
side effect is that it will... The question is: Will this be
acceptable?
I believe you may hit several problems. You may want to talk to support
about this, but I suppose the answer will be that it's unsupported and
can potentially lead to corruption or bad query results...

I'll check this out on a test instance. See what the queries with JOINS will return, I doubt the results will be good. As long as we're doing SELECT/read-only then there should not be any corruption though? Then again the idea of a misconfigured client screwing up the tables with incorrect locales sounds bad enough.

The correct solution is probably to push the migrations and get this over with as fast as possible. The sooner we're in utf only land, the better.

Regards,

Aleksander Kamenik
System Administrator
Krediidiinfo AS
an Experian Company
Phone: +372 665 9649
Email: aleksander (AT) krediidiinfo (DOT) ee

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.