1DBD::Gofer::Policy::BasUes(e3r)Contributed Perl DocumentDaBtDi:o:nGofer::Policy::Base(3)
2
3
4

NAME

6       DBD::Gofer::Policy::Base - Base class for DBD::Gofer policies
7

SYNOPSIS

9         $dbh = DBI->connect("dbi:Gofer:transport=...;policy=...", ...)
10

DESCRIPTION

12       DBD::Gofer can be configured via a 'policy' mechanism that allows you
13       to fine-tune the number of round-trips to the Gofer server.  The
14       policies are grouped into classes (which may be subclassed) and
15       referenced by the name of the class.
16
17       The DBD::Gofer::Policy::Base class is the base class for all the policy
18       classes and describes all the individual policy items.
19
20       The Base policy is not used directly. You should use a policy class
21       derived from it.
22

POLICY CLASSES

24       Three policy classes are supplied with DBD::Gofer:
25
26       DBD::Gofer::Policy::pedantic is most 'transparent' but slowest because
27       it makes more  round-trips to the Gofer server.
28
29       DBD::Gofer::Policy::classic is a reasonable compromise - it's the
30       default policy.
31
32       DBD::Gofer::Policy::rush is fastest, but may require code changes in
33       your applications.
34
35       Generally the default "classic" policy is fine. When first testing an
36       existing application with Gofer it is a good idea to start with the
37       "pedantic" policy first and then switch to "classic" or a custom
38       policy, for final testing.
39

POLICY ITEMS

41       These are temporary docs: See the source code for list of policies and
42       their defaults.
43
44       In a future version the policies and their defaults will be defined in
45       the pod and parsed out at load-time.
46
47       See the source code to this module for more details.
48

POLICY CUSTOMIZATION

50       XXX This area of DBD::Gofer is subject to change.
51
52       There are three ways to customize policies:
53
54       Policy classes are designed to influence the overall behaviour of
55       DBD::Gofer with existing, unaltered programs, so they work in a
56       reasonably optimal way without requiring code changes. You can
57       implement new policy classes as subclasses of existing policies.
58
59       In many cases individual policy items can be overridden on a case-by-
60       case basis within your application code. You do this by passing a
61       corresponding "<go_<policy_name">> attribute into DBI methods by your
62       application code.  This let's you fine-tune the behaviour for special
63       cases.
64
65       The policy items are implemented as methods. In many cases the methods
66       are passed parameters relating to the DBD::Gofer code being executed.
67       This means the policy can implement dynamic behaviour that varies
68       depending on the particular circumstances, such as the particular
69       statement being executed.
70

AUTHOR

72       Tim Bunce, <http://www.tim.bunce.name>
73

75       Copyright (c) 2007, Tim Bunce, Ireland. All rights reserved.
76
77       This module is free software; you can redistribute it and/or modify it
78       under the same terms as Perl itself. See perlartistic.
79
80
81
82perl v5.28.1                      2013-06-24       DBD::Gofer::Policy::Base(3)
Impressum