Menu
▾
▴
[Firebird-devel] [ firebird-Bugs-1015925 ] Can't open database with MBCS/Extended characters in name
|
From: SourceForge.net <no...@so...> - 2005-04-15 13:38:06
|
Bugs item #1015925, was opened at 2004-08-25 09:10 Message generated for change (Comment added) made by asfernandes You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109028&aid=1015925&group_id=9028 Category: Core Engine Group: Confirmed Bug Status: Open Resolution: None Priority: 5 Submitted By: Adriano dos Santos Fernandes (asfernandes) Assigned to: Nobody/Anonymous (nobody) Summary: Can't open database with MBCS/Extended characters in name Initial Comment: Extended characters in filenames isn't converted from connection charset to OS code page. This causes wrong filenames when creating databases with a charset different from the OS code page. ---------------------------------------------------------------------- >Comment By: Adriano dos Santos Fernandes (asfernandes) Date: 2005-04-15 10:38 Message: Logged In: YES user_id=940451 While with the new INTL architecture this bug can be fixed, there is one big problem yet. How to maintain compatibility with pre-ODS11 databases and backups? Many system tables store filenames with charset NONE. To fix this bug the fields that store filenames should be changed to charset UNICODE_FSS. Then the server can convert between the client charset and UNICODE_FSS and between UNICODE_FSS and the system code page. ---------------------------------------------------------------------- Comment By: Percy Li (percyboy) Date: 2005-04-15 02:16 Message: Logged In: YES user_id=908241 Can you tell me: Do you have a plan to solve this bug? Would it be included in the next release? Thanks! I am planning to use Firebird but met the bug stopping my work.(as described in bug # 1182700) ---------------------------------------------------------------------- Comment By: Sean Leyne (seanleyne) Date: 2005-04-14 12:24 Message: Logged In: YES user_id=71163 To further elaborate, based on comments noted in tracker # 1182700, the problem is not limited to the filename itself but the full path\filename string. ---------------------------------------------------------------------- Comment By: Sean Leyne (seanleyne) Date: 2004-11-14 19:43 Message: Logged In: YES user_id=71163 Updating the description/summary to better reflect the true nature of the bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109028&aid=1015925&group_id=9028 |
