firebird/firebird-mirror
firebird/firebird-mirror
8
0
Fork 1
mirror of https://github.com/FirebirdSQL/firebird.git synced 2025-01-22 20:03:02 +01:00
Code Issues

Misc.

Browse Source
This commit is contained in:
robocop 2008-12-25 06:16:08 +00:00
parent 39d4c7578d
commit 45da536360
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
doc/README.connection_string_charset.txt
View File

@ -2,8 +2,8 @@ Author: Adriano dos Santos Fernandes <adrianosf@uol.com.br>
Date: 2008-12-15 Date: 2008-12-15
Before FB 2.5, filenames used in the connection string are always passed from the client to the Before FB 2.5, filenames used in the connection string are always passed from the client to the
server without any conversion. On the server, that filenames are used with OS API functions without server without any conversion. On the server, those filenames are used with OS API functions without
any conversion too. This creates the situation where filenames using non-ASCII characters do not any conversion, too. This creates the situation where filenames using non-ASCII characters do not
interoperate well when the client and the server are different OS or even same OS using different interoperate well when the client and the server are different OS or even same OS using different
codepages. codepages.
@ -11,24 +11,24 @@ The problem is addressed in FB 2.5 in the following way:
The filename is considered, by default, to be on the OS codepage. The filename is considered, by default, to be on the OS codepage.
A new DPB is introduced, named isc_dpb_utf8_filename. It meaning is to change rule above, so FB A new DPB is introduced, named isc_dpb_utf8_filename. Its meaning is to change the rule above, so FB
should consider the passed filename as being in UTF-8. should consider the passed filename as being in UTF-8.
If a v2.5 (or superior) client is communicating with a remote server inferior than v2.5, and If a v2.5 (or newer) client is communicating with a remote server older than v2.5, and
isc_dpb_utf8_filename was used, the client converts the filename from UTF-8 to the client isc_dpb_utf8_filename was used, the client converts the filename from UTF-8 to the client
codepage and pass that filename to the server. The client removes isc_dpb_utf8_filename DPB. codepage and passes that filename to the server. The client removes isc_dpb_utf8_filename DPB.
This guarantees backward compatibility where people are using the same codepage on the client and This guarantees backward compatibility when people are using the same codepage on the client and
server OS. server OS.
If a v2.5 (or superior) client is communicating with a v2.5 (or superior) server, and If a v2.5 (or newer) client is communicating with a v2.5 (or newer) server, and
isc_dpb_utf8_filename was not used, the client converts the filename from the OS codepage to isc_dpb_utf8_filename was not used, the client converts the filename from the OS codepage to
UTF-8 and inserts the isc_dpb_utf8_filename DPB. If isc_dpb_utf8_filename was used, the client just UTF-8 and inserts the isc_dpb_utf8_filename DPB. If isc_dpb_utf8_filename was used, the client just
pass the original filename withing the DPB to the server. So the client always pass to the server passes the original filename withing the DPB to the server. So the client always passes to the server
UTF-8 filename and the isc_dpb_utf8_filename DPB. an UTF-8 filename and the isc_dpb_utf8_filename DPB.
The filename received on the server is subject to the same rules above. But note that v2.5 client The filename received on the server is subject to the same rules above. But note that v2.5 client
may automatically coverts the filename and insert the DPB. Client inferior than v2.5 do not, may automatically convert the filename and insert the DPB. Clients older than v2.5 do not,
so the received filenames are going to be considered as on the server codepage. We again guarantees so the received filenames are going to be considered as on the server codepage. We again guarantee
backward compatibility when client and server codepage are the same. backward compatibility when client and server codepage are the same.
The OS codepage and UTF-8 may not be the better choice for filenames. For example, if you had a The OS codepage and UTF-8 may not be the better choice for filenames. For example, if you had a
@ -37,8 +37,8 @@ correctly edit a script (or any file) using multiple character sets (codepages).
encode any Unicode character as ASCII characters on the connection string filename. That's encode any Unicode character as ASCII characters on the connection string filename. That's
accomplished using the symbol #. It is a prefix for an Unicode code point number (in hexadecimal accomplished using the symbol #. It is a prefix for an Unicode code point number (in hexadecimal
format, like U+XXXX notation). You should write it in this way: #XXXX with X being 0-9, a-f, A-F. format, like U+XXXX notation). You should write it in this way: #XXXX with X being 0-9, a-f, A-F.
If you want to use the literal #, you could use ## or #0023 (the code point number of it). If you want to use the literal #, you could use ## or #0023 (the code point number for it).
That character is interpreted with this new semantics at the server even if the client is inferior That character is interpreted with this new semantics at the server even if the client is older
than v2.5. than v2.5.
The OS codepage used for conversions is: The OS codepage used for conversions is: