Can't open database with MBCS/Extended characters in name [CORE316]

[firebird-automations]

Submitted by: @asfernandes

Is duplicated by CORE2172
Is duplicated by CORE3876
Relate to CORE4993

Votes: 1

SFID: 1015925#⁠
Submitted By: asfernandes

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.

Commits: 84dfa0e

[firebird-automations]

Commented by: Alice F. Bird (firebirds)

Date: 2005-10-05 02:02
Sender: seanleyne
Logged In: YES
user_id=71163

Dmitry,

Yes, the 2 issues are the same.

Although #⁠839060 was opened first, I would suggest that it be closed as "duplicate" since this item since to better describe the problem.

[firebird-automations]

Commented by: Alice F. Bird (firebirds)

Date: 2005-10-03 21:12
Sender: dimitr
Logged In: YES
user_id=61270

BTW, is SF #⁠839060 related to this issue?

[firebird-automations]

Commented by: Alice F. Bird (firebirds)

Date: 2005-04-15 15:38
Sender: asfernandes
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.

[firebird-automations]

Commented by: Alice F. Bird (firebirds)

Date: 2005-04-15 07:16
Sender: percyboy
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)

[firebird-automations]

Commented by: Alice F. Bird (firebirds)

Date: 2005-04-14 17:24
Sender: seanleyne
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.

[firebird-automations]

Commented by: Alice F. Bird (firebirds)

Date: 2004-11-14 22:43
Sender: seanleyne
Logged In: YES
user_id=71163

Updating the description/summary to better reflect the true
nature of the bug.

[firebird-automations]

Modified by: @pcisar

Workflow: jira [ 10340 ] => Firebird [ 14580 ]

[firebird-automations]

Modified by: Sean Leyne (seanleyne)

Link: This issue is duplicated by CORE2172 [ CORE2172 ]

[firebird-automations]

Commented by: Henri Gourvest (hgourvest)

I think the aliases.conf file is also concerned by this issue.

[firebird-automations]

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Beta 1 [ 10251 ]

assignee: Adriano dos Santos Fernandes [ asfernandes ]

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

[firebird-automations]

Modified by: Sean Leyne (seanleyne)

Link: This issue is duplicated by CORE3876 [ CORE3876 ]

[firebird-automations]

Modified by: Sean Leyne (seanleyne)

Link: This issue relate to CORE4993 [ CORE4993 ]

[firebird-automations]

Modified by: Sean Leyne (seanleyne)

description: SFID: 1015925#⁠
Submitted By: asfernandes

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.

=>

SFID: 1015925#⁠
Submitted By: asfernandes

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.

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test