Re: Re: pdo design

Ard Biesheuvel wrote:

Wez Furlong wrote: You might turn commit() into a NOP and raise the error on rollback() only, as it's the responsibility of the user to choose a DB that fits his needs. This would enhance portability IMO

Doesnt sound like a good idea to me. Since the default is auto commit all is well. If you move out of auto commit mode then you do this for the exact reason of potentially wanting to rollback. But anyways maybe I didnt understand what you were trying to say as you only mention commit() but not getting out of auto commit mode.

These can (perhaps should) be extension level functions and not methods of the PDO class, unless they happen to be uniform API's across the majority of APIs.

I think most databases allow SQL statements to carry out these tasks, which makes this one a non-issue.

Yup. The main piece of information needed is the version number since sometimes these maintaince query syntaxes change. One thing that you cant query for though which atleast seem RDBMS do is fetch the additional metadata provided inside a result set. Like the table name(s) etc. Would be nice if PDO would provide this information as well. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07