DBD-Sybase
view release on metacpan or search on metacpan
Minor fixes to allow building on Windows.
Fixed syntax error at compile time for some compilers
Allow database names with special chars in the name.
Change to ct_data_info() to flag an error in case the CS_IODESC returned
doesn't include a valid text pointer - this happens if the text/image column
is nullable and has not been initialized in the database.
Release 1.14
Fix bad size handling for unicode data.
Remove default charset setting to utf8 (this had been done in 1.11 as part of
improved utf8 handling, but has negative side-effects. If unicode handling is needed
then set "charset=utf8" as part of the connection string.
Enforce the fact that utf8/unicode handling only works with OpenClient 15.x or later.
Release 1.13
Fix for incorrect UTF8 handling when retrieving UNICODE data (Jean-Pierre Rupp).
Release 1.12
Bug/Typo/Compatibility fixes with various versions of OpenClient.
Experimental: Handle in/out parameters (Merijn Broeren)
=item charset
Specify the character set that the client uses.
$dbh = DBI->connect("dbi:Sybase:charset=iso_1",
$user, $passwd);
The default charset used depends on the locale that the application runs
in. If you wish to interact with unicode varaiables (see syb_enable_utf8, below) then
you should set charset=utf8. Note however that this means that Sybase will expect all
data sent to it for char/varchar columns to be encoded in utf8 (e.g. sending iso8859-1 characters
like e-grave, etc).
=item language
Specify the language that the client uses.
$dbh = DBI->connect("dbi:Sybase:language=us_english",
$user, $passwd);
The syb_disconnect_in_child attribute attempts to correct this - the default is for this
attribute to be False - thereby inhibitting the closing of the connection(s) when
the current process ID doesn't match the process ID that created the connection.
Default: off
=item syb_enable_utf8 (bool)
If this attribute is set then DBD::Sybase will convert UNIVARCHAR, UNICHAR,
and UNITEXT data to Perl's internal utf-8 encoding when they are
retrieved. Updating a unicode column will cause Sybase to convert any incoming
data from utf-8 to its internal utf-16 encoding.
This feature requires OpenClient 15.x to work.
Default: off
=back
=head2 Statement Handle Attributes
( run in 0.423 second using v1.01-cache-2.11-cpan-88abd93f124 )