Hi!
Wez Furlong wrote:
> What purpose does this serve exactly?
PDO::FETCH_KEYS is supposed to be a "generalized" form of the existing
PDO::FETCH_KEY_PAIR. The latter is limited to two column results and
organises it into key=>value.
PDO::FETCH_2D is an IMHO better strategy than the existing
ATTR_FETCH_TABLE_NAMES. The latter includes two "information tokens"
into one datum (the array index).
> Why do we need to allocate an empty string for every database connection?
The empty string is the default value for the attribute. NULL actually
has a different meaning. Of course, the actual implementation of a
default value is open for change, of course.
> Why do we need this in the core?
> There's a lot of manipulation being done here that is better suited to
> happen in PHP script land where it's safer and easier to maintain.
PDO::FETCH_2D is *NOT* easily implemented in PHP as it needs information
unavailable before.
PDO::FETCH_KEYS is just a generalization of the existing
PDO::FETCH_KEY_PAIR.
What do you mean by "manipulation"? I only intended to implement fetch
modes I need.
HPO
PS: Please notice the updated patch.