perldoc ResourcePool::Command::DBI::Execute


ResourcePool::Command::DBI::Execute - A DBI command to execute non select statements.


use ResourcePool::Command::DBI::Execute;

# simple usage
my $cmd = ResourcePool::Command::DBI::Execute->new();
my $pool; # ResourcePool setup not shown here
eval {
    , 'insert into test (id, name, value) values (?, ?, ?)'
    , 1 , 'xy', '15'

# pre configured usage
my $cmd2 = ResourcePool::Command::DBI::Execute->new(
  'insert into test (id, name, value) values (?, ?, ?)'
  , { 1 => {type => SQL_INTEGER}
    , 2 => {type => SQL_VARCHAR}
    , 3 => {type => SQL_VARCHAR}
  , prepare_cached => 1

my $i;
for ($i = 0; $i < 1000; $i++) {
  $pool->execute($cmd2, $i, "name $i", "value $i");

# using named bind parameters and output parameters
my $cmd3 = ResourcePool::Command::DBI::Execute->new(
    'insert into test (name, value) values (:name, :value)' 
  . ' returning id into :id'
  , { ':id' => {max_len => 50}} 
    # max_len identifies an output parameter

my $id;
  , { ':name' => 'a name'
    , ':value' => 'a value'
    , ':id' => \$id # output parameter passed by ref


This command can be used to execute non select statements in a DBI database using the ResourcePool command execution environment.

In order to understand this Class, and more importantly this document, you need to know a few terms I use in this document, if you are new to this class you should read the TERMS sections first.

If the command was executed successfully (without error being raised) the transaction will be committed.

ResourcePool::Command::DBI::Execute->new($SQL, \%bindconf, @attr)

Instantiates a new Execute object, all parameters are optional, the only restriction is that if you want to specify a bind configuration you have also to specify a SQL.


If you specify a SQL string at construction, you can not change it during lifetime of this object. The most common reason to do so is if you want to execute this command more then once, than you do not need to pass the SQL every time. The second reasons is because the only possible way to pass a bind configuration to the Execute object is at construction, and you are only allowed to specify a bind configuration if you have also specified a SQL.


If you have passed a SQL command to the constructor you can also pass a hash reference to bind configuration.

The hash is expected to use a placeholder name as key and an other hash reference as value. If you use for example '?' (position parameters) than the key for that would be 1 for the first '?' in you SQL, 2 for the second and so on. If you use named parameters the name of this parameter is the key to the bind configuration hash.

For each placeholder you can define a second hash which can hold configuration for this single placeholder:


Specifies the type of the placeholder. For example SQL_INTEGER for numeric values.


Specifies the maximum space allocated for output parameters. If you want to use output parameters (for example when calling stored procedures) you MUST specify this attribute with an appropriate value.

By defining this value, the Execute calls changes the way it binds the parameters to bind_param_inout which is required for output parameters. If you use output parameters you MUST pass a reference to a scalar which should be used to store the output parameter as bind parameter when calling execute().


Options which do change the way Execute() works can be specified as last argument. There is currently only one such option:

$pool->execute($SQL, @bindparam)


If you haven't specified a SQL string on construction, you have to specify it as first argument to the execute method.


Positional parameters which should be bound before executing the statement. It is also possible to use named parameters as described below.


IF you have specified a SQL statement at construction of this object, you can not specify another when calling the execute() method.


Named parameters to be bound before executing the statement. The last example from the synopsis uses this technique. Don't forget to pass the reference to a scalar for output parameters.


SQL statement

Thats the most easy and important part of each Execute command (surprise, surprise). There are two ways specifying a SQL command for this class, the first is to pass it to the execute() method of the pool as shown in the 'simple usage' above. The second is to pass it to the constructor of the Execute class, this will enable you to specify more information for this SQL like bind parameter types. If you have passed the SQL to the constructor, you can not pass another SQL to the execute() method.

bind parameter

Bind parameters are, like in plain DBI, the values associated to the placeholders in the SQL. placeholders can currently passed to the execute() method as shown in 'pre configured usage' above.

bind configuration

There are two things which can currently be configured for bind parameters, those are the type to bind the parameter as and configure a particular parameter to be an in/out parameter by setting a max_len value. This settings can be supplied to the constructor if you have also specified a SQL to the constructor. The 'pre configured usage' above illustrates the configuration of types, the 'using named bind parameters and output parameters' shows how to configure an in/out parameter.


Attributes are configurations which are interpreted by the Execute class itself, those are not passed to the DBI but may influence the way the Execute() class uses the DBI. Attributes can be specified in the name => value syntax as last argument to the constructor. The 'pre configured usage' example above uses the prepare_cached attribute.



Currently every executed command is it's own transaction. There is no possibility to join more than one pre-existing command into one transaction. Macros will make this possible, however they are under construction.



Copyright (C) 2001-2003 by Markus Winand <>

This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.


Do not use offset for pagination. Learn why.


Last modification:
Mon Jan 31 15:15:34 2011
Informationen zu E-Commerce und Mediengesetz