1 | =head1 NAME |
1 | =head1 NAME |
2 | |
2 | |
3 | PApp::SQL - absolutely easy yet fast and powerful sql access |
3 | PApp::SQL - absolutely easy yet fast and powerful sql access. |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
7 | use PApp::SQL; |
7 | use PApp::SQL; |
8 | |
8 | |
… | |
… | |
13 | my $st = sql_insertid |
13 | my $st = sql_insertid |
14 | sql_exec "insert into ... values (?, ?)", $v1, $v2; |
14 | sql_exec "insert into ... values (?, ?)", $v1, $v2; |
15 | my $a = sql_fetch "select a from ..."; |
15 | my $a = sql_fetch "select a from ..."; |
16 | sql_fetch \my($a, $b), "select a,b ..."; |
16 | sql_fetch \my($a, $b), "select a,b ..."; |
17 | |
17 | |
18 | sql_exists "name from table where name like 'a%'" |
18 | sql_exists "table where name like 'a%'" |
19 | or die "a* required but not existent"; |
19 | or die "a* required but not existent"; |
20 | |
20 | |
21 | my $db = new PApp::SQL::Database "", "DBI:mysql:test", "user", "pass"; |
21 | my $db = new PApp::SQL::Database "", "DBI:mysql:test", "user", "pass"; |
22 | local $PApp::SQL::DBH = $db->checked_dbh; # does 'ping' |
22 | local $PApp::SQL::DBH = $db->checked_dbh; # does 'ping' |
23 | |
23 | |
… | |
… | |
27 | |
27 | |
28 | This module provides you with easy-to-use functions to execute sql |
28 | This module provides you with easy-to-use functions to execute sql |
29 | commands (using DBI). Despite being easy to use, they are also quite |
29 | commands (using DBI). Despite being easy to use, they are also quite |
30 | efficient and allow you to write faster programs in less lines of code. It |
30 | efficient and allow you to write faster programs in less lines of code. It |
31 | should work with anything from perl-5.004_01 onwards, but I only support |
31 | should work with anything from perl-5.004_01 onwards, but I only support |
32 | 5.005+. |
32 | 5.005+. UTF8 handling (the C<sql_u*> family of functions) will only be |
|
|
33 | effective with perl version 5.006 and beyond. |
33 | |
34 | |
34 | If the descriptions here seem terse or if you always wanted to know |
35 | If the descriptions here seem terse or if you always wanted to know |
35 | what PApp is then have a look at the PApp module which uses this module |
36 | what PApp is then have a look at the PApp module which uses this module |
36 | extensively but also provides you with a lot more gimmicks to play around |
37 | extensively but also provides you with a lot more gimmicks to play around |
37 | with to help you create cool applications ;) |
38 | with to help you create cool applications ;) |
… | |
… | |
43 | use DBI (); |
44 | use DBI (); |
44 | |
45 | |
45 | BEGIN { |
46 | BEGIN { |
46 | use base qw(Exporter DynaLoader); |
47 | use base qw(Exporter DynaLoader); |
47 | |
48 | |
48 | $VERSION = 0.122; |
49 | $VERSION = 0.13; |
49 | @EXPORT = qw( |
50 | @EXPORT = qw( |
50 | sql_exec sql_fetch sql_fetchall sql_exists sql_insertid $sql_exec |
51 | sql_exec sql_fetch sql_fetchall sql_exists sql_insertid $sql_exec |
|
|
52 | sql_uexec sql_ufetch sql_ufetchall sql_uexists |
51 | ); |
53 | ); |
52 | @EXPORT_OK = qw( |
54 | @EXPORT_OK = qw( |
53 | connect_cached |
55 | connect_cached |
54 | ); |
56 | ); |
55 | |
57 | |
… | |
… | |
67 | =over 4 |
69 | =over 4 |
68 | |
70 | |
69 | =item $sql_exec |
71 | =item $sql_exec |
70 | |
72 | |
71 | Since the C<sql_exec> family of functions return a statement handle there |
73 | Since the C<sql_exec> family of functions return a statement handle there |
72 | must eb another way to test the return value of the C<execute> call. This |
74 | must be another way to test the return value of the C<execute> call. This |
73 | global variable contains the result of the most recent call to C<execute> |
75 | global variable contains the result of the most recent call to C<execute> |
74 | done by this module. |
76 | done by this module. |
75 | |
77 | |
76 | =item $PApp::SQL::DBH |
78 | =item $PApp::SQL::DBH |
77 | |
79 | |
… | |
… | |
109 | __LINE__ work fine as well). |
111 | __LINE__ work fine as well). |
110 | |
112 | |
111 | The reason C<$id> is necessary is that you might specify special connect |
113 | The reason C<$id> is necessary is that you might specify special connect |
112 | arguments or special flags, or you might want to configure your $DBH |
114 | arguments or special flags, or you might want to configure your $DBH |
113 | differently than maybe other applications requesting the same database |
115 | differently than maybe other applications requesting the same database |
114 | connection. If none of this is becessary for your application you can |
116 | connection. If none of this is necessary for your application you can |
115 | leave $id empty (i.e. ""). |
117 | leave C<$id> empty (i.e. ""). |
116 | |
118 | |
117 | If specified, C<$connect> is a callback (e.g. a coderef) that will be |
119 | If specified, C<$connect> is a callback (e.g. a coderef) that will be |
118 | called each time a new connection is being established, with the new |
120 | called each time a new connection is being established, with the new |
119 | C<$dbh> as first argument. |
121 | C<$dbh> as first argument. |
120 | |
122 | |
121 | Examples: |
123 | Examples: |
122 | |
124 | |
123 | # try your luck opening the papp database without access info |
125 | # try your luck opening the papp database without access info |
124 | $dbh = connect_cached __FILE__, "DBI:mysql:papp"; |
126 | $dbh = connect_cached __FILE__, "DBI:mysql:papp"; |
|
|
127 | |
|
|
128 | Mysql-specific behaviour: The default setting of |
|
|
129 | C<mysql_client_found_rows> is TRUE, you can overwrite this, though. |
125 | |
130 | |
126 | =cut |
131 | =cut |
127 | |
132 | |
128 | sub connect_cached { |
133 | sub connect_cached { |
129 | my ($id, $dsn, $user, $pass, $flags, $connect) = @_; |
134 | my ($id, $dsn, $user, $pass, $flags, $connect) = @_; |
130 | # the following line is duplicated in PApp::SQL::Database::new |
135 | # the following line is duplicated in PApp::SQL::Database::new |
131 | $id = "$id\0$dsn\0$user\0$pass"; |
136 | $id = "$id\0$dsn\0$user\0$pass"; |
132 | unless ($dbcache{$id} && $dbcache{$id}->ping) { |
137 | unless ($dbcache{$id} && $dbcache{$id}->ping) { |
133 | #warn "connecting to ($dsn|$user|$pass|$flags)\n";#d# |
|
|
134 | # first, nuke our statement cache (sooory ;) |
138 | # first, nuke our statement cache (sooory ;) |
135 | cachesize cachesize 0; |
139 | cachesize cachesize 0; |
|
|
140 | |
|
|
141 | # then make mysql behave more standardly by default |
|
|
142 | $dsn =~ /^[Dd][Bb][Ii]:mysql:/ |
|
|
143 | and $dsn !~ /;mysql_client_found_rows/ |
|
|
144 | and $dsn .= ";mysql_client_found_rows=1"; |
|
|
145 | |
136 | # then connect anew |
146 | # then connect anew |
137 | $dbcache{$id} = |
147 | $dbcache{$id} = |
138 | eval { DBI->connect($dsn, $user, $pass, $flags) } |
148 | eval { DBI->connect($dsn, $user, $pass, $flags) } |
139 | || eval { DBI->connect($dsn, $user, $pass, $flags) } |
149 | || eval { DBI->connect($dsn, $user, $pass, $flags) } |
140 | || die "unable to connect to database $dsn: $DBI::errstr\n"; |
150 | || die "unable to connect to database $dsn: $DBI::errstr\n"; |
… | |
… | |
143 | $dbcache{$id}; |
153 | $dbcache{$id}; |
144 | } |
154 | } |
145 | |
155 | |
146 | =item $sth = sql_exec [dbh,] [bind-vals...,] "sql-statement", [arguments...] |
156 | =item $sth = sql_exec [dbh,] [bind-vals...,] "sql-statement", [arguments...] |
147 | |
157 | |
|
|
158 | =item $sth = sql_uexec <see sql_exec> |
|
|
159 | |
148 | C<sql_exec> is the most important and most-used function in this module. |
160 | C<sql_exec> is the most important and most-used function in this module. |
149 | |
161 | |
150 | Runs the given sql command with the given parameters and returns the |
162 | Runs the given sql command with the given parameters and returns the |
151 | statement handle. The command and the statement handle will be cached |
163 | statement handle. The command and the statement handle will be cached |
152 | (with the database handle and the sql string as key), so prepare will be |
164 | (with the database handle and the sql string as key), so prepare will be |
153 | called only once for each distinct sql call (please keep in mind that the |
165 | called only once for each distinct sql call (please keep in mind that the |
154 | returned statement will always be the same, so, if you call C<sql_exec> |
166 | returned statement will always be the same, so, if you call C<sql_exec> |
155 | with the same dbh and sql-statement twice (e.g. in a subroutine you |
167 | with the same dbh and sql-statement twice (e.g. in a subroutine you |
156 | called), the statement handle for the first call mustn't be used. |
168 | called), the statement handle for the first call mustn't not be in use |
|
|
169 | anymore, as the subsequent call will re-use the handle. |
157 | |
170 | |
158 | The database handle (the first argument) is optional. If it is missing, |
171 | The database handle (the first argument) is optional. If it is missing, |
159 | C<sql_exec> first tries to use the variable C<$DBH> in the current (= |
172 | C<sql_exec> first tries to use the variable C<$DBH> in the current (= |
160 | calling) package and, if that fails, it tries to use database handle in |
173 | calling) package and, if that fails, it tries to use database handle in |
161 | C<$PApp::SQL::DBH>, which you can set before calling these functions. |
174 | C<$PApp::SQL::DBH>, which you can set before calling these functions. |
162 | |
175 | |
163 | The actual return value from the C<$sth->execute> call is stored in the |
176 | The actual return value from the C<$sth->execute> call is stored in the |
164 | package-global (and exported) variable C<$sql_exec>. |
177 | package-global (and exported) variable C<$sql_exec>. |
165 | |
178 | |
166 | If any error occurs C<sql_exec> will throw an exception. |
179 | If any error occurs C<sql_exec> will throw an exception. |
|
|
180 | |
|
|
181 | C<sql_uexec> is similar to C<sql_exec> but upgrades all input arguments to |
|
|
182 | utf8 before calling the C<execute> method. |
167 | |
183 | |
168 | Examples: |
184 | Examples: |
169 | |
185 | |
170 | # easy one |
186 | # easy one |
171 | my $st = sql_exec "select name, id from table where id = ?", $id; |
187 | my $st = sql_exec "select name, id from table where id = ?", $id; |
… | |
… | |
181 | sql_exec $dbh, "update file set name = ?", "oops.txt"; |
197 | sql_exec $dbh, "update file set name = ?", "oops.txt"; |
182 | |
198 | |
183 | |
199 | |
184 | =item sql_fetch <see sql_exec> |
200 | =item sql_fetch <see sql_exec> |
185 | |
201 | |
|
|
202 | =item sql_ufetch <see sql_uexec> |
|
|
203 | |
186 | Execute a sql-statement and fetch the first row of results. Depending on |
204 | Execute an sql-statement and fetch the first row of results. Depending on |
187 | the caller context the row will be returned as a list (array context), or |
205 | the caller context the row will be returned as a list (array context), or |
188 | just the first columns. In table form: |
206 | just the first columns. In table form: |
189 | |
207 | |
190 | CONTEXT RESULT |
208 | CONTEXT RESULT |
191 | void () |
209 | void () |
… | |
… | |
202 | |
220 | |
203 | my($name, $amount) = sql_fetch "select ...", args... |
221 | my($name, $amount) = sql_fetch "select ...", args... |
204 | |
222 | |
205 | ... and it's still quite fast unless you fetch large amounts of data. |
223 | ... and it's still quite fast unless you fetch large amounts of data. |
206 | |
224 | |
|
|
225 | C<sql_ufetch> is similar to C<sql_fetch> but upgrades all input values to |
|
|
226 | utf8 and forces all result values to utf8 (this does I<not> include result |
|
|
227 | parameters, only return values. Using bind variables in cinjunction with |
|
|
228 | sql_u* functions results in undefined behaviour). |
|
|
229 | |
207 | =item sql_fetchall <see sql_exec> |
230 | =item sql_fetchall <see sql_exec> |
|
|
231 | |
|
|
232 | =item sql_ufetchall <see sql_uexec> |
208 | |
233 | |
209 | Similarly to C<sql_fetch>, but all result rows will be fetched (this is |
234 | Similarly to C<sql_fetch>, but all result rows will be fetched (this is |
210 | of course inefficient for large results!). The context is ignored (only |
235 | of course inefficient for large results!). The context is ignored (only |
211 | list context makes sense), but the result still depends on the number of |
236 | list context makes sense), but the result still depends on the number of |
212 | columns in the result: |
237 | columns in the result: |
… | |
… | |
224 | |
249 | |
225 | for (sql_fetchall "select name, age, place from user") { |
250 | for (sql_fetchall "select name, age, place from user") { |
226 | my ($name, $age, $place) = @$_; |
251 | my ($name, $age, $place) = @$_; |
227 | } |
252 | } |
228 | |
253 | |
|
|
254 | C<sql_ufetchall> is similar to C<sql_fetchall> but upgrades all input |
|
|
255 | values to utf8 and forces all result values to utf8 (see the caveats in |
|
|
256 | the description of C<sql_ufetch>, though). |
|
|
257 | |
229 | =item sql_exists "<table> where ...", args... |
258 | =item sql_exists "<table_references> where <where_condition>...", args... |
|
|
259 | |
|
|
260 | =item sql_uexists <see sql_exists> |
230 | |
261 | |
231 | Check wether the result of the sql-statement "select xxx from |
262 | Check wether the result of the sql-statement "select xxx from |
232 | $first_argument" would be empty or not (that is, imagine the string |
263 | $first_argument" would be empty or not (that is, imagine the string |
233 | "select * from" were prepended to your statement (it isn't)). Should work |
264 | "select * from" were prepended to your statement (it isn't)). Should work |
234 | with every database but can be quite slow, except on mysql, where this |
265 | with every database but can be quite slow, except on mysql, where this |
235 | should be quite fast. |
266 | should be quite fast. |
|
|
267 | |
|
|
268 | C<sql_uexists> is similar to C<sql_exists> but upgrades all parameters to |
|
|
269 | utf8. |
236 | |
270 | |
237 | Examples: |
271 | Examples: |
238 | |
272 | |
239 | print "user 7 exists!\n" |
273 | print "user 7 exists!\n" |
240 | if sql_exists "user where id = ?", 7; |
274 | if sql_exists "user where id = ?", 7; |
… | |
… | |
314 | |
348 | |
315 | package PApp::SQL::Database; |
349 | package PApp::SQL::Database; |
316 | |
350 | |
317 | =head2 THE DATABASE CLASS |
351 | =head2 THE DATABASE CLASS |
318 | |
352 | |
319 | Again (sigh) the problem of persistency. What do you do when you have to serialize on object |
353 | Again (sigh) the problem of persistency. What do you do when you have |
320 | that contains (or should contain) a database handle? Short answer: you don't. Long answer: |
354 | to serialize on object that contains (or should contain) a database |
|
|
355 | handle? Short answer: you don't. Long answer: you can embed the necessary |
321 | you can embed the necessary information to recreate the dbh when needed. |
356 | information to recreate the dbh when needed. |
322 | |
357 | |
323 | The C<PApp::SQL::Database> class does that, in a relatively efficient |
358 | The C<PApp::SQL::Database> class does that, in a relatively efficient |
324 | fashion: the overhead is currently a single method call per access (you |
359 | fashion: the overhead is currently a single method call per access (you |
325 | can cache the real dbh if you want). |
360 | can cache the real dbh if you want). |
326 | |
361 | |