Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Win32 - Can't connect database placed in a directory with Japanese characters [CORE2172] #2603

Open
firebird-automations opened this issue Nov 7, 2008 · 10 comments
Open

Win32 - Can't connect database placed in a directory with Japanese characters [CORE2172] #2603

firebird-automations opened this issue Nov 7, 2008 · 10 comments
Labels
affect-version: 2.0.3 affect-version: 2.0.4 affect-version: 2.1.0 component: engine priority: major type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: James Ang (jang)

Duplicates CORE316
Is duplicated by CORE3172
Relate to CORE4993

Votes: 5

The Firebird FDB is placed in this folder:
C:\日本語フォルダ\Data\

Hence the full path to the FDB is:
C:\日本語フォルダ\Data\FIREBIRDSUPERSERVERALIAS.FDB

Calls to isc_attach_database() will fail with something like "Unspecified database name".

I reproduced this issue on my development environment (Windows XP Professional SP3 (US English locale)), but the problem was found while testing on a Japanese OS.

I can also reproduce the problem with an FDB named: 日本語フォルダ.FDB placed in C:\
C:\日本語フォルダ.FDB

It was very easy to reproduce the problem.

The workaround is to ensure that the full path to the FDB does not contain non-ASCII characters especially Unicode characters.

This problem was found in the versions of Firebird I tested (specified in this bug report else where).
@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

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

resolution: Duplicate [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

Link: This issue duplicates CORE316 [ CORE316 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

I'm reopening this case, because it may be fixed only when we use the Windows Wide API functions.
It's not a duplicate report.

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

status: Closed [ 6 ] => Reopened [ 4 ]

resolution: Duplicate [ 3 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

Link: This issue is duplicated by CORE3172 [ CORE3172 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @aafemt

This issue is not limited to Japanese characters but appear on any path or file name containing symbols from outside of current ANSI code page. And using CreateFileW() indeed is necessary to solve it on Windows. On Linux fopen accepts utf-8 encoded string.

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

It depends on Windows ANSI codepage. If it's UTF-8, and using the new utf8-dpb, it should work.

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

Link: This issue relate to CORE4993 [ CORE4993 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @aafemt

UTF-8 cannot be set as ANSI codepage in Windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affect-version: 2.0.3 affect-version: 2.0.4 affect-version: 2.1.0 component: engine priority: major type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@firebird-automations