if (not exists $dbi_attrs->{odbc_cursortype}) {
# turn on support for multiple concurrent statements, unless overridden
$dbi_attrs->{odbc_cursortype} = 2;
- my $connected = defined $self->_dbh;
- $self->disconnect;
- $self->ensure_connected if $connected;
+ $self->disconnect; # resetting dbi attrs, so have to reconnect
+ $self->ensure_connected;
$self->_set_dynamic_cursors;
}
}
sub _set_dynamic_cursors {
my $self = shift;
- my $dbh = $self->_dbh;
+ my $dbh = $self->_get_dbh;
eval {
local $dbh->{RaiseError} = 1;
my $self = shift;
my $sql_rowset_size = shift || 2;
- $self->_dbh->{odbc_SQL_ROWSET_SIZE} = $sql_rowset_size;
+ $self->_get_dbh->{odbc_SQL_ROWSET_SIZE} = $sql_rowset_size;
}
-=head2 connect_call_use_mars
+=head2 connect_call_use_MARS
Use as:
- on_connect_call => 'use_mars'
+ on_connect_call => 'use_MARS'
Use to enable a feature of SQL Server 2005 and later, "Multiple Active Result
Sets". See L<DBD::ODBC::FAQ/Does DBD::ODBC support Multiple Active Statements?>
=cut
-sub connect_call_use_mars {
+sub connect_call_use_MARS {
my $self = shift;
my $dsn = $self->_dbi_connect_info->[0];
if ($dsn !~ /MARS_Connection=/) {
$self->_dbi_connect_info->[0] = "$dsn;MARS_Connection=Yes";
- my $connected = defined $self->_dbh;
+ my $was_connected = defined $self->_dbh;
$self->disconnect;
- $self->ensure_connected if $connected;
+ $self->ensure_connected if $was_connected;
}
}