1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
DBIx::Connector
DBIx::Connector provides a simple interface for fast and safe DBI
connection and transaction management. Connecting to a database can be
expensive; you don't want your application to re-connect every time you
need to run a query. The efficient thing to do is to hang on to a
database handle to maintain a connection to the database in order to
minimize that overhead. DBIx::Connector lets you do that without having
to worry about dropped or corrupted connections.
You might be familiar with Apache::DBI and with the DBI's
"connect_cached()" constructor. DBIx::Connector serves a similar need,
but does a much better job. How is it different? I'm glad you asked!
* Fork Safety
Like Apache::DBI, but unlike "connect_cached()", DBIx::Connector
create a new database connection if a new process has been "fork"ed.
This happens all the time under mod_perl, in POE applications, and
elsewhere. Works best with DBI 1.614 and higher.
* Thread Safety
Unlike Apache::DBI or "connect_cached()", DBIx::Connector will
create a new database connection if a new thread has been spawned.
As with "fork"ing, spawning a new thread can break database
connections.
* Works Anywhere
Unlike Apache::DBI, DBIx::Connector runs anywhere -- inside of
mod_perl or not. Why limit yourself?
* Explicit Interface
DBIx::Connector has an explicit interface. There is none of the
magical action-at-a-distance crap that Apache::DBI is guilty of, and
no global caching. I've personally diagnosed a few issues with
Apache::DBI's magic, and killed it off in two different projects in
favor of "connect_cached()", only to be tripped up by other gotchas.
No more.
* Optimistic Execution
If you use "run()" and "txn()", the database handle will be passed
without first pinging the server. For the 99% or more of the time
when the database is just there, you'll save a ton of overhead
without the ping.
DBIx::Connector's other feature is transaction management. Borrowing an
interface from DBIx::Class, DBIx::Connector offers an API that
efficiently handles the scoping of database transactions so that you
needn't worry about managing the transaction yourself. Even better, it
offers an API for savepoints if your database supports them. Within a
transaction, you can scope savepoints to behave like subtransactions, so
that you can save some of your work in a transaction even if part of it
fails. See "txn()" and "svp()" for the goods.
INSTALLATION
This is a Perl module distribution. It should be installed with
whichever tool you use to manage your installation of Perl, e.g. any of
cpanm .
cpan .
cpanp -i .
Consult http://www.cpan.org/modules/INSTALL.html for further
instruction. Should you wish to install this module manually, the
procedure is
perl Makefile.PL
make
make test
make install
COPYRIGHT AND LICENSE
Copyright (c) 2009-2013 David E. Wheeler. Some Rights Reserved.
This module is free software; you can redistribute it and/or modify it
under the same terms as Perl itself.
|
