Re: pdo comments
| From: | Wez Furlong | Date: | Mon, 18 Oct 2004 21:49:47 +0000 |
| Subject: | Re: pdo comments | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-1471@lists.php.net to get a copy of this message | ||
> 4) do you think it would make sense to convert empty strings on insert
> as well if PDO_ATTR_ORACLE_NULLS is set and prepared statements are used
IMO, no.
> 5) in mdb[2] when you call $mdb->autoCommit(false) it starts an implicit
> transaction. after every call to $mdb->commit() or $mdb->rollback() the
> transaction is ended and a new implicit transaction is started. with
> $mdb->autoCommit(true) the implicit transaction is ended if one is still
> open. how does this relate to how things are done in pdo?
Ummm, I'll have to look at the code again before I answer with authority.
In general though, "thou shalt not toggle autocommit at run time in
portable applications", and "thou shall enable autocommit only at
handle creation time in portable applications".
> 6) Does it make sense to have fetch() as part of the statement object
> instead of having result sets having their own class?
It's less painful to use having the the result set merged into the
statement handle, so IMO (and that of the perl guys) this is better
than having a separate result set class.
--Wez.