Re: Matching PDO_SQLite features with SQLite3 extension

From: Date: Thu, 24 Aug 2017 10:25:30 +0000
Subject: Re: Matching PDO_SQLite features with SQLite3 extension
References: 1 2 3 4 5 6 7  Groups: php.internals 
Request: Send a blank email to internals+get-100297@lists.php.net to get a copy of this message
On Thu, 24 Aug 2017 11:55:10 +0200 / "Christoph M. Becker" <cmbecker69@gmx.de> said : > It seems to me this is rather simple: if a feature is uncontroversial, > it doesn't need an RFC. Since nobody objected against PR #2528, it > was merged (after some weeks). However, there have been objections > against PR #2698, so an RFC appears to be appropriate. Cool, that's a rule that makes sense :) maybe it should be in the contributing guide? Can someone give me RFC power on the wiki (my account is "bohwaz")? Thanks. Should I include the proposal for adding the PDOStatement::readOnly() method? Should it be named PDOStatement::sqliteReadOnly() or readOnly()? I have no idea. Or should it even be PDO::sqliteIsReadOnly($statement)? I think that adding read-only and read-write opening options for SQLite PDO shouldn't raise any eyebrows here as it doesn't involve any new method, so I'll do a separate patch for that. Anyone objecting? Cheers.

« previous php.internals (#100297) next »