Re: PDO SQLite: statement attributes for SQL text retrieval

> > I don't feel strongly about one way or the other. I'm happy to revise this > into a function if the consensus is that everyone is more comfortable with > parameters allowing either pre/post binding state to be returned, probably > defaulting to the pre-binding state. > I don't think 2 methods are needed for functionality that is functionally > very similar. > > That being said, I still prefer an attribute because this isn't an > actionable function (like sqliteCreateFunction) but rather something that > retrieves information, which to me seems more appropriate for attribute > retrieval similar to Pdo\Pgsql::ATTR_RESULT_MEMORY_SIZE for example. > I don't think this warrants its own function and the value of setting a > return type seems minimal. > One more thing :) Looking at pdo/PgSQL and pdo/SQlite they both limit custom functions to things that change data. However, pdo/MySQL and pdo/Firebird break the convention, each has a single custom function for info retrieval, so there isn't technically as convention universally followed convention here. -- Ilia Alshanetsky Technologist, CTO, Entrepreneur E: ilia@ilia.ws T: @iliaa B: http://ilia.ws