ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/PApp-SQL/SQL.pm
(Generate patch)

Comparing PApp-SQL/SQL.pm (file contents):
Revision 1.39 by root, Sun Jun 21 03:30:00 2009 UTC vs.
Revision 1.42 by root, Sat Oct 7 15:54:35 2017 UTC

… …
25 25
26=head1 DESCRIPTION 26=head1 DESCRIPTION
27 27
28This module provides you with easy-to-use functions to execute sql 28This module provides you with easy-to-use functions to execute sql
29commands (using DBI). Despite being easy to use, they are also quite 29commands (using DBI). Despite being easy to use, they are also quite
30efficient and allow you to write faster programs in less lines of code. It 30efficient and allow you to write faster programs in fewer lines of
31should work with anything from perl-5.004_01 onwards, but I only support 31code. It should work with anything from perl-5.004_01 onwards, but I only
325.005+. UTF8 handling (the C<sql_u*> family of functions) will only be 32support 5.005+. UTF8 handling (the C<sql_u*> family of functions) will
33effective with perl version 5.006 and beyond. 33only be effective with perl version 5.006 and beyond.
34 34
35If the descriptions here seem terse or if you always wanted to know 35If the descriptions here seem terse or if you always wanted to know
36what PApp is then have a look at the PApp module which uses this module 36what PApp is then have a look at the PApp module which uses this module
37extensively but also provides you with a lot more gimmicks to play around 37extensively but also provides you with a lot more gimmicks to play around
38with to help you create cool applications ;) 38with to help you create cool applications ;)
… …
45use DBI (); 45use DBI ();
46 46
47BEGIN { 47BEGIN {
48 use base qw(Exporter DynaLoader); 48 use base qw(Exporter DynaLoader);
49 49
50 $VERSION = '1.05'; 50 $VERSION = '2.001';
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
62boot2 DBI::SQL_VARCHAR, DBI::SQL_INTEGER, DBI::SQL_DOUBLE;
63
62our $sql_exec; # last result of sql_exec's execute call 64our $sql_exec; # last result of sql_exec's execute call
63our $DBH; # the default database handle 65our $DBH; # the default database handle
64our $Database; # the current SQL::Database object, if applicable 66our $Database; # the current SQL::Database object, if applicable
65 67
66our %dbcache; 68our %dbcache;
… …
99 101
100(not exported by by default) 102(not exported by by default)
101 103
102Connect to the database given by C<($dsn,$user,$pass)>, while using the 104Connect to the database given by C<($dsn,$user,$pass)>, while using the
103flags from C<$flags>. These are just the same arguments as given to 105flags from C<$flags>. These are just the same arguments as given to
104C<DBI->connect>. 106C<< DBI->connect >>.
105 107
106The database handle will be cached under the unique id 108The database handle will be cached under the unique id
107C<$id|$dsn|$user|$pass>. If the same id is requested later, the 109C<$id|$dsn|$user|$pass>. If the same id is requested later, the
108cached handle will be checked (using ping), and the connection will 110cached handle will be checked (using ping), and the connection will
109be re-established if necessary (be sure to prefix your application or 111be re-established if necessary (be sure to prefix your application or
… …
181database handle in C<$PApp::SQL::DBH>, which you can set before calling 183database handle in C<$PApp::SQL::DBH>, which you can set before calling
182these functions. 184these functions.
183 185
184=end comment 186=end comment
185 187
186The actual return value from the C<$sth->execute> call is stored in the 188The actual return value from the C<< $sth->execute >> call is stored in
187package-global (and exported) variable C<$sql_exec>. 189the package-global (and exported) variable C<$sql_exec>.
188 190
189If any error occurs C<sql_exec> will throw an exception. 191If any error occurs C<sql_exec> will throw an exception.
190 192
191C<sql_uexec> is similar to C<sql_exec> but upgrades all input arguments to 193C<sql_uexec> is similar to C<sql_exec> but upgrades all input arguments to
192UTF-8 before calling the C<execute> method. 194UTF-8 before calling the C<execute> method.
… …
359 361
360=cut 362=cut
361 363
362reinitialize; 364reinitialize;
363 365
366=head2 Type Deduction
367
368Since every database driver seems to deduce parameter types differently,
369usually wrongly, and at leats in the case of DBD::mysql, different in
370every other release or so, and this can and does lead to data corruption,
371this module does type deduction itself.
372
373What does it mean? Simple - sql parameters for placeholders will be
374explicitly marked as SQL_VARCHAR, SQL_INTEGER or SQL_DOUBLE the first time
375a statement is prepared.
376
377To force a specific type, you can either continue to use e.g. sql casts,
378or you can make sure to consistently use strings or numbers. To make a
379perl scalar look enough like a string or a number, use this when passing
380it to sql_exec or a similar functions:
381
382 "$string" # to pass a string
383 $num+0 # to pass a number
384
385=cut
386
364package PApp::SQL::Database; 387package PApp::SQL::Database;
365 388
366=head2 The Database Class 389=head2 The Database Class
367 390
368Again (sigh) the problem of persistency. What do you do when you have 391Again (sigh) the problem of persistency. What do you do when you have

Diff Legend

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