ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/Coro-Mysql/README
(Generate patch)

Comparing Coro-Mysql/README (file contents):
Revision 1.4 by root, Sun Feb 20 10:35:10 2011 UTC vs.
Revision 1.6 by root, Mon Mar 4 11:40:52 2019 UTC

1NAME 1NAME
2 Coro::Mysql - let other threads run while doing mysql requests 2 Coro::Mysql - let other threads run while doing mysql/mariadb requests
3 3
4SYNOPSIS 4SYNOPSIS
5 use Coro::Mysql; 5 use Coro::Mysql;
6 6
7 my $DBH = Coro::Mysql::unblock DBI->connect (...); 7 my $DBH = Coro::Mysql::unblock DBI->connect (...);
8 8
9DESCRIPTION 9DESCRIPTION
10 (Note that in this manual, "thread" refers to real threads as 10 (Note that in this manual, "thread" refers to real threads as
11 implemented by the Coro module, not to the built-in windows process 11 implemented by the Coro module, not to the built-in windows process
12 emulation which unfortunately is also called "threads") 12 emulation which unfortunately is also called "threads").
13 13
14 This module "patches" DBD::mysql database handles so that they do not 14 This module replaces the I/O handlers for a database connection, with
15 block the whole process, but only the thread that they are used in. 15 the effect that "patched" database handles no longer block all threads
16 of a process, but only the thread that does the request. It should work
17 for both DBD::mysql and DBD::MariaDB connections and a wide range of
18 mariadb/mysql client libraries.
16 19
17 This can be used to make parallel sql requests using Coro, or to do 20 This can be used to make parallel sql requests using Coro, or to do
18 other stuff while mysql is rumbling in the background. 21 other stuff while mariadb is rumbling in the background.
19 22
20 CAVEAT 23 CAVEAT
21 Note that this module must be linked against exactly the same (shared, 24 Note that this module must be linked against exactly the same (shared,
22 possibly not working with all OSes) libmysqlclient library as 25 possibly not working with all OSes) libmariadb/libmysqlclient library as
23 DBD::mysql, otherwise it will not work. 26 DBD::MariaDB/DBD::mysql, otherwise it will not work.
24 27
25 Also, while this module makes database handles non-blocking, you still 28 Also, while this module makes database handles non-blocking, you still
26 cannot run multiple requests in parallel on the same database handle. If 29 cannot run multiple requests in parallel on the same database handle. If
27 you want to run multiple queries in parallel, you have to create 30 you want to run multiple queries in parallel, you have to create
28 multiple database connections, one for each thread that runs queries. 31 multiple database connections, one for each thread that runs queries.
29 Not doing so can corrupt your data - use a Coro::Semaphore when in 32 Not doing so can corrupt your data - use a Coro::Semaphore to protetc
30 doubt. 33 access to a shared database handle when in doubt.
31 34
32 If you make sure that you never run two or more requests in parallel, 35 If you make sure that you never run two or more requests in parallel,
33 you can freely share the database handles between threads, of course. 36 you can freely share the database handles between threads, of course.
34
35 Also, this module uses a number of "unclean" techniques (patching an
36 internal libmysql structure for one thing) and was initially hacked
37 within a few hours on a long flight to Malaysia.
38
39 It does, however, check whether it indeed got the structure layout
40 correct, so you should expect perl exceptions or early crashes as
41 opposed to data corruption when something goes wrong during patching.
42 37
43 SPEED 38 SPEED
44 This module is implemented in XS, and as long as mysqld replies quickly 39 This module is implemented in XS, and as long as mysqld replies quickly
45 enough, it adds no overhead to the standard libmysql communication 40 enough, it adds no overhead to the standard libmysql communication
46 routines (which are very badly written, btw.). In fact, since it has a 41 routines (which are very badly written, btw.). In fact, since it has a
… …
68 handle unusable. As far as Coro::Mysql is concerned, the handle can be 63 handle unusable. As far as Coro::Mysql is concerned, the handle can be
69 safely destroyed, but it's not clear how mysql itself will react to a 64 safely destroyed, but it's not clear how mysql itself will react to a
70 cancellation. 65 cancellation.
71 66
72FUNCTIONS 67FUNCTIONS
73 Coro::Mysql offers a single user-accessible function: 68 Coro::Mysql offers these functions, the only one that oyu usually need
69 is "unblock":
74 70
75 $DBH = Coro::Mysql::unblock $DBH 71 $DBH = Coro::Mysql::unblock $DBH
76 This function takes a DBI database handles and "patches" it so it 72 This function takes a DBI database handles and "patches" it so it
77 becomes compatible to Coro threads. 73 becomes compatible to Coro threads.
78 74
… …
87 It is also safe to pass "undef", so code like this is works as 83 It is also safe to pass "undef", so code like this is works as
88 expected: 84 expected:
89 85
90 my $dbh = DBI->connect ($database, $user, $pass)->Coro::Mysql::unblock 86 my $dbh = DBI->connect ($database, $user, $pass)->Coro::Mysql::unblock
91 or die $DBI::errstr; 87 or die $DBI::errstr;
88
89 $bool = Coro::Mysql::is_unblocked $DBH
90 Returns true iff the database handle was successfully patched for
91 non-blocking operations.
92
93 $bool = Coro::Mysql::have_ev
94 Returns true if this Coro::Mysql installation is compiled with
95 special support for EV or not.
96
97 Even if compiled in, it will only be used if EV is actually the
98 AnyEvent event backend.
92 99
93USAGE EXAMPLE 100USAGE EXAMPLE
94 This example uses PApp::SQL and Coro::on_enter to implement a function 101 This example uses PApp::SQL and Coro::on_enter to implement a function
95 "with_db", that connects to a database, uses "unblock" on the resulting 102 "with_db", that connects to a database, uses "unblock" on the resulting
96 handle and then makes sure that $PApp::SQL::DBH is set to the 103 handle and then makes sure that $PApp::SQL::DBH is set to the
… …
136 } for 1..10; 143 } for 1..10;
137 144
138SEE ALSO 145SEE ALSO
139 Coro, PApp::SQL (a user friendly but efficient wrapper around DBI). 146 Coro, PApp::SQL (a user friendly but efficient wrapper around DBI).
140 147
148HISTORY
149 This module was initially hacked together within a few hours on a long
150 flight to Malaysia, and seems to have worked ever since, with minor
151 adjustments for newer libmysqlclient libraries.
152
153 Well, at least until mariadb introduced the new Pluggable Virtual IO API
154 in mariadb 10.3, which changed and broke everything. On the positive
155 side, the old system was horrible to use, as many GNU/Linux
156 distributions forgot to include the required heaqder files and there
157 were frequent small changes, while the new PVIO system seems to be
158 "official" and hopefully better supported.
159
141AUTHOR 160AUTHOR
142 Marc Lehmann <schmorp@schmorp.de> 161 Marc Lehmann <schmorp@schmorp.de>
143 http://home.schmorp.de/ 162 http://home.schmorp.de/
144 163

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines