/usr/share/doc/firebird
Author: Adriano dos Santos Fernandes <adrianosf@uol.com.br> Date: 2008-12-15 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, those filenames are used with OS API functions without 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 codepages. The problem is addressed in FB 2.5 in the following way: The filename is considered, by default, to be on the OS codepage. 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. 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 codepage and passes that filename to the server. The client removes isc_dpb_utf8_filename DPB. This guarantees backward compatibility when people are using the same codepage on the client and server OS. 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 UTF-8 and inserts the isc_dpb_utf8_filename DPB. If isc_dpb_utf8_filename was used, the client just passes the original filename withing the DPB to the server. So the client always passes to the server 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 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 guarantee backward compatibility when client and server codepage are the same. The OS codepage used for conversions is: - Windows: The Windows ANSI code page - Others: UTF-8 Updated for 2.5 Beta 2: 2008-07-11 These rules are now valid for string DPB items too.
.
Edit
..
Edit
CHANGELOG.md
Edit
Firebird-3-QuickStart.pdf
Edit
Firebird-4.0.6-ReleaseNotes.pdf
Edit
IDPLicense.txt
Edit
IPLicense.txt
Edit
README.DiskSpaceAllocation
Edit
README.Fedora
Edit
README.IPv6
Edit
README.NTSecurity
Edit
README.Optimizer.txt
Edit
README.SecureRemotePassword.html
Edit
README.Win32LibraryInstallation.txt
Edit
README.Win9X_NT_embedding
Edit
README.build.macosx.md
Edit
README.build.mingw.html
Edit
README.build.msvc.html
Edit
README.build.posix.html
Edit
README.coding.style
Edit
README.connection_string_charset.txt
Edit
README.connection_strings
Edit
README.external_routines.txt
Edit
README.fb_cancel_operation
Edit
README.fb_shutdown
Edit
README.fbsvcmgr
Edit
README.garbage_collector
Edit
README.gbak
Edit
README.incompatibilities.3to4.txt
Edit
README.incompatibilities.txt
Edit
README.instsvc
Edit
README.intl
Edit
README.isql_enhancements.txt
Edit
README.makefiles
Edit
README.md
Edit
README.modern_cpp.md
Edit
README.monitoring_tables
Edit
README.online_validation
Edit
README.performance_monitoring
Edit
README.plugins.html
Edit
README.providers.html
Edit
README.raw_devices
Edit
README.read_consistency.md
Edit
README.read_password_from_file
Edit
README.replication.md
Edit
README.security_database.txt
Edit
README.services_extension
Edit
README.session_idle_timeouts
Edit
README.sha1
Edit
README.statement_timeouts
Edit
README.superclassic
Edit
README.trace_services
Edit
README.transaction_at_snapshot.md
Edit
README.trusted_authentication
Edit
README.user.embedded
Edit
README.user.troubleshooting
Edit
README.wire.compression.html
Edit
README.xnet
Edit
sample
Edit
sql.extensions
Edit
udf_replace.sql
Edit
udf_replace.txt
Edit