coming back to that topic, if anybody reading this will try the same.

found out that all stored procedures have to be recompiled, otherwise
there will be transliteration errors.

After recompiling offending stored procs, everything is fine.

  
  
-- 
Mit freundlichen Grüssen,

André Knappstein, EDV und Controlling
Verwaltungs- und Erlebniszentrum Marina Rünthe
beta Eigenheim GmbH
Hafenweg 4
59192 Bergkamen-Rünthe

Durchwahl: +49 2389 9240 140

~~~Ihre Nachricht~~~

JC> On 7/20/07, André Knappstein, Controlling
JC> <[EMAIL PROTECTED]> wrote:
>> 1.)
>> update
>>   rdb$database
>> set
>>   rdb$character_set_name = "WIN1252";

JC> This isn't required. This is default charset for new columns if it's
JC> not specified.

>> 2.)
>> update
>>   rdb$Fields
>> set
>>   rdb$character_set_ID = 53
>> where
>>   rdb$character_set_ID = 21;
>>
>> 3.)
>> update
>>   rdb$function_arguments
>> set
>>   rdb$character_set_ID = 53
>> where
>>   rdb$character_set_ID = 21;

JC> This the quick&dirty version. But if no error is reported during
JC> backup&restore, it's fine.

>>
>> Then backing up, and restoring into a new database.
>> Quite brutal, I know, but that worked perfectly.
>>
>> But - before I try that with the production databases - did I miss
>> something important which might beat me only much later??
>>
>> Is there maybe a much more simple way to switch character set for a
>> database?

JC> Changing domain.

>> Thanks,
>> André
>>
>>
>> ~~~Ihre Nachricht~~~
>>
>> >> One questions remains, though.
>> >> If ISO8859_1 is not suitable for that purpose, why have I never been
>> >> noticing this before? I mean, why do the other drivers/providers
>> >> translate those bytes correctly to a Euro sign?
>>
>> DH> ISO 8859-1 and WIN-1252 are almost exactly the same, except that where 
>> ISO
>> DH> 8859-1 has some control codes, WIN-1252 has a few extra letters (like 
>> U+2020
>> DH> †, etc) -- one of those extra letters is the Euro sign.
>>
>> DH> Many applications, however (especially Windows applications) treat ISO
>> DH> 8859-1 as being synonymous with WIN-1252, so that's probably why it 
>> worked
>> DH> in those other cases. .NET is not so lenient, however, and something 
>> marked
>> DH> as ISO 8859-1 to .NET will not be able to contain a Euro symbol.
>>
>> DH> Dean.
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Firebird-net-provider mailing list
>> Firebird-net-provider@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>>




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Reply via email to