Re: DBI prepare and fetch
Many thanks for your replies. I think the reason for prepare is the
statement handle on return so it can be passed adcross with subroutine
calls. Passing a statement handle is less memory intensive than passing
the SQL around. Please correct me if I am wrong.
.
Relevant Pages
- Re: Derived type name as a dummy argument - possible?
... Dan Nagle wrote: ... but passing a derived type name as a dummy argument does not ... data structures without having to modify the generic subroutine. ... (comp.lang.fortran) - Re: null terminated strings
... a call to those in a subroutine. ... The compiler will then insure that you're passing the proper data type. ... I'm having trouble thinking of the few times that I passed something to a routine, and had the routine treat it as another type of data. ... Passing the address of an AST handler routine when setting up an AST timer routine was interesting. ... (comp.os.vms) - Re: Does the order of declarations matter?
... >> subroutine sub ... >No, these are two different types of arguments - IIRC, one is assumed-size ... passing it as a separate argument. ... an explicit interface is always safer. ... (comp.lang.fortran) - Difference between passing a number and a variable to a subroutine
... I just found out that Fortran distinguishes between passing a variable and actual numbers to a subroutine. ... results in a compiler error: ... (comp.lang.fortran) - Re: DBI prepare and fetch
... > statement handle on return so it can be passed adcross with subroutine ... Passing a statement handle is less memory intensive than passing ... How do you bind parameters to a statemnet ... (comp.lang.perl.misc) |
|