… | |
… | |
25 | |
25 | |
26 | =head1 DESCRIPTION |
26 | =head1 DESCRIPTION |
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 fewer lines of |
31 | should work with anything from perl-5.004_01 onwards, but I only support |
31 | code. It should work with anything from perl-5.004_01 onwards, but I only |
32 | 5.005+. UTF8 handling (the C<sql_u*> family of functions) will only be |
32 | support 5.005+. UTF8 handling (the C<sql_u*> family of functions) will |
33 | effective with perl version 5.006 and beyond. |
33 | only be effective with perl version 5.006 and beyond. |
34 | |
34 | |
35 | 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 |
36 | 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 |
37 | 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 |
38 | with to help you create cool applications ;) |
38 | with to help you create cool applications ;) |
… | |
… | |
45 | use DBI (); |
45 | use DBI (); |
46 | |
46 | |
47 | BEGIN { |
47 | BEGIN { |
48 | use base qw(Exporter DynaLoader); |
48 | use base qw(Exporter DynaLoader); |
49 | |
49 | |
50 | $VERSION = '1.04'; |
50 | $VERSION = '2.002'; |
51 | @EXPORT = qw( |
51 | @EXPORT = qw( |
52 | sql_exec sql_fetch sql_fetchall sql_exists sql_insertid $sql_exec |
52 | sql_exec sql_fetch sql_fetchall sql_exists sql_insertid $sql_exec |
53 | sql_uexec sql_ufetch sql_ufetchall sql_uexists |
53 | sql_uexec sql_ufetch sql_ufetchall sql_uexists |
54 | ); |
54 | ); |
55 | @EXPORT_OK = qw( |
55 | @EXPORT_OK = qw( |
… | |
… | |
57 | ); |
57 | ); |
58 | |
58 | |
59 | bootstrap PApp::SQL $VERSION; |
59 | bootstrap PApp::SQL $VERSION; |
60 | } |
60 | } |
61 | |
61 | |
|
|
62 | boot2 DBI::SQL_VARCHAR, DBI::SQL_INTEGER, DBI::SQL_DOUBLE; |
|
|
63 | |
62 | our $sql_exec; # last result of sql_exec's execute call |
64 | our $sql_exec; # last result of sql_exec's execute call |
63 | our $DBH; # the default database handle |
65 | our $DBH; # the default database handle |
64 | our $Database; # the current SQL::Database object, if applicable |
66 | our $Database; # the current SQL::Database object, if applicable |
65 | |
67 | |
66 | our %dbcache; |
68 | our %dbcache; |
… | |
… | |
99 | |
101 | |
100 | (not exported by by default) |
102 | (not exported by by default) |
101 | |
103 | |
102 | Connect to the database given by C<($dsn,$user,$pass)>, while using the |
104 | Connect to the database given by C<($dsn,$user,$pass)>, while using the |
103 | flags from C<$flags>. These are just the same arguments as given to |
105 | flags from C<$flags>. These are just the same arguments as given to |
104 | C<DBI->connect>. |
106 | C<< DBI->connect >>. |
105 | |
107 | |
106 | The database handle will be cached under the unique id |
108 | The database handle will be cached under the unique id |
107 | C<$id|$dsn|$user|$pass>. If the same id is requested later, the |
109 | C<$id|$dsn|$user|$pass>. If the same id is requested later, the |
108 | cached handle will be checked (using ping), and the connection will |
110 | cached handle will be checked (using ping), and the connection will |
109 | be re-established if necessary (be sure to prefix your application or |
111 | be re-established if necessary (be sure to prefix your application or |
… | |
… | |
181 | database handle in C<$PApp::SQL::DBH>, which you can set before calling |
183 | database handle in C<$PApp::SQL::DBH>, which you can set before calling |
182 | these functions. |
184 | these functions. |
183 | |
185 | |
184 | =end comment |
186 | =end comment |
185 | |
187 | |
186 | The actual return value from the C<$sth->execute> call is stored in the |
188 | The actual return value from the C<< $sth->execute >> call is stored in |
187 | package-global (and exported) variable C<$sql_exec>. |
189 | the package-global (and exported) variable C<$sql_exec>. |
188 | |
190 | |
189 | If any error occurs C<sql_exec> will throw an exception. |
191 | If any error occurs C<sql_exec> will throw an exception. |
190 | |
192 | |
191 | C<sql_uexec> is similar to C<sql_exec> but upgrades all input arguments to |
193 | C<sql_uexec> is similar to C<sql_exec> but upgrades all input arguments to |
192 | UTF-8 before calling the C<execute> method. |
194 | UTF-8 before calling the C<execute> method. |
… | |
… | |
296 | Returns the last automatically created key value. It must be executed |
298 | Returns the last automatically created key value. It must be executed |
297 | directly after executing the insert statement that created it. This is |
299 | directly after executing the insert statement that created it. This is |
298 | what is actually returned for various databases. If your database is |
300 | what is actually returned for various databases. If your database is |
299 | missing, please send me an e-mail on how to implement this ;) |
301 | missing, please send me an e-mail on how to implement this ;) |
300 | |
302 | |
|
|
303 | mariadb: first C<AUTO_INCREMENT> column set to NULL |
301 | mysql: first C<AUTO_INCREMENT> column set to NULL |
304 | mysql: first C<AUTO_INCREMENT> column set to NULL |
302 | postgres: C<oid> column (is there a way to get the last SERIAL?) |
305 | postgres: C<oid> column (is there a way to get the last SERIAL?) |
303 | sybase: C<IDENTITY> column of the last insert (slow) |
306 | sybase: C<IDENTITY> column of the last insert (slow) |
304 | informix: C<SERIAL> or C<SERIAL8> column of the last insert |
307 | informix: C<SERIAL> or C<SERIAL8> column of the last insert |
305 | sqlite: C<last_insert_rowid()> |
308 | sqlite: C<last_insert_rowid()> |
… | |
… | |
311 | sub sql_insertid($) { |
314 | sub sql_insertid($) { |
312 | my $sth = shift or Carp::croak "sql_insertid requires a statement handle"; |
315 | my $sth = shift or Carp::croak "sql_insertid requires a statement handle"; |
313 | my $dbh = $sth->{Database}; |
316 | my $dbh = $sth->{Database}; |
314 | my $driver = $dbh->{Driver}{Name}; |
317 | my $driver = $dbh->{Driver}{Name}; |
315 | |
318 | |
|
|
319 | $driver eq "MariaDB" and return $sth->{mariadb_insertid}; |
316 | $driver eq "mysql" and return $sth->{mysql_insertid}; |
320 | $driver eq "mysql" and return $sth->{mysql_insertid}; |
317 | $driver eq "Pg" and return $sth->{pg_oid_status}; |
321 | $driver eq "Pg" and return $sth->{pg_oid_status}; |
318 | $driver eq "Sybase" and return sql_fetch ($dbh, 'SELECT @@IDENTITY'); |
322 | $driver eq "Sybase" and return sql_fetch ($dbh, 'SELECT @@IDENTITY'); |
319 | $driver eq "Informix" and return $sth->{ix_sqlerrd}[1]; |
323 | $driver eq "Informix" and return $sth->{ix_sqlerrd}[1]; |
320 | $driver eq "SQLite" and return sql_fetch ($dbh, 'SELECT last_insert_rowid ()'); |
324 | $driver eq "SQLite" and return sql_fetch ($dbh, 'SELECT last_insert_rowid ()'); |
321 | |
325 | |
322 | Carp::croak "sql_insertid does not support the dbd driver '$driver', at"; |
326 | $dbh->last_insert_id (undef, undef, undef, undef) |
323 | } |
327 | } |
324 | |
328 | |
325 | =item [old-size] = cachesize [new-size] |
329 | =item [old-size] = cachesize [new-size] |
326 | |
330 | |
327 | Returns (and possibly changes) the LRU cache size used by C<sql_exec>. The |
331 | Returns (and possibly changes) the LRU cache size used by C<sql_exec>. The |
… | |
… | |
359 | |
363 | |
360 | =cut |
364 | =cut |
361 | |
365 | |
362 | reinitialize; |
366 | reinitialize; |
363 | |
367 | |
|
|
368 | =head2 Type Deduction |
|
|
369 | |
|
|
370 | Since every database driver seems to deduce parameter types differently, |
|
|
371 | usually wrongly, and at leats in the case of DBD::mysql, different in |
|
|
372 | every other release or so, and this can and does lead to data corruption, |
|
|
373 | this module does type deduction itself. |
|
|
374 | |
|
|
375 | What does it mean? Simple - sql parameters for placeholders will be |
|
|
376 | explicitly marked as SQL_VARCHAR, SQL_INTEGER or SQL_DOUBLE the first time |
|
|
377 | a statement is prepared. |
|
|
378 | |
|
|
379 | To force a specific type, you can either continue to use e.g. sql casts, |
|
|
380 | or you can make sure to consistently use strings or numbers. To make a |
|
|
381 | perl scalar look enough like a string or a number, use this when passing |
|
|
382 | it to sql_exec or a similar functions: |
|
|
383 | |
|
|
384 | "$string" # to pass a string |
|
|
385 | $num+0 # to pass a number |
|
|
386 | |
|
|
387 | =cut |
|
|
388 | |
364 | package PApp::SQL::Database; |
389 | package PApp::SQL::Database; |
365 | |
390 | |
366 | =head2 The Database Class |
391 | =head2 The Database Class |
367 | |
392 | |
368 | Again (sigh) the problem of persistency. What do you do when you have |
393 | Again (sigh) the problem of persistency. What do you do when you have |