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.22 by root, Sun Apr 7 16:22:56 2002 UTC vs.
Revision 1.23 by root, Sun Apr 7 16:23:56 2002 UTC

… …
163statement handle. The command and the statement handle will be cached 163statement handle. The command and the statement handle will be cached
164(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
165called only once for each distinct sql call (please keep in mind that the 165called only once for each distinct sql call (please keep in mind that the
166returned statement will always be the same, so, if you call C<sql_exec> 166returned statement will always be the same, so, if you call C<sql_exec>
167with the same dbh and sql-statement twice (e.g. in a subroutine you 167with the same dbh and sql-statement twice (e.g. in a subroutine you
168called), the statement handle for the first call mustn't be used. 168called), the statement handle for the first call mustn't not be in use
169anymore, as the subsequent call will re-use the handle.
169 170
170The database handle (the first argument) is optional. If it is missing, 171The database handle (the first argument) is optional. If it is missing,
171C<sql_exec> first tries to use the variable C<$DBH> in the current (= 172C<sql_exec> first tries to use the variable C<$DBH> in the current (=
172calling) package and, if that fails, it tries to use database handle in 173calling) package and, if that fails, it tries to use database handle in
173C<$PApp::SQL::DBH>, which you can set before calling these functions. 174C<$PApp::SQL::DBH>, which you can set before calling these functions.

Diff Legend

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