… | |
… | |
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.05'; |
50 | $VERSION = '2.0'; |
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( |
56 | connect_cached |
56 | connect_cached |
57 | ); |
57 | ); |
58 | |
58 | |
59 | bootstrap PApp::SQL $VERSION; |
59 | bootstrap PApp::SQL $VERSION; |
60 | } |
60 | } |
|
|
61 | |
|
|
62 | boot2 DBI::SQL_VARCHAR, DBI::SQL_INTEGER, DBI::SQL_DOUBLE; |
61 | |
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 | |
… | |
… | |
359 | |
361 | |
360 | =cut |
362 | =cut |
361 | |
363 | |
362 | reinitialize; |
364 | reinitialize; |
363 | |
365 | |
|
|
366 | =head2 Type Deduction |
|
|
367 | |
|
|
368 | Since every database driver seems to deduce parameter types differently, |
|
|
369 | usually wrongly, and at leats in the case of DBD::mysql, different in |
|
|
370 | every other release or so, and this can and does lead to data corruption, |
|
|
371 | this module does type deduction itself. |
|
|
372 | |
|
|
373 | What does it mean? Simple - sql parameters for placeholders will be |
|
|
374 | explicitly marked as SQL_VARCHAR, SQL_INTEGER or SQL_DOUBLE the first time |
|
|
375 | a statement is prepared. |
|
|
376 | |
|
|
377 | To force a specific type, you can either continue to use e.g. sql casts, |
|
|
378 | or you can make sure to consistently use strings or numbers. To make a |
|
|
379 | perl scalar look enough like a string or a number, use this when passing |
|
|
380 | it 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 | |
364 | package PApp::SQL::Database; |
387 | package PApp::SQL::Database; |
365 | |
388 | |
366 | =head2 The Database Class |
389 | =head2 The Database Class |
367 | |
390 | |
368 | Again (sigh) the problem of persistency. What do you do when you have |
391 | Again (sigh) the problem of persistency. What do you do when you have |