hi Ilia,
So you basically say that the worries and wishes raised here are
simply irrelevant and at the end of the day you decide what PDO can or
cannot be?
I'm very disappointed by these two commits. I don't think it is the
way we should develop PDO and it is clear that I'm not the only one to
Same, I am disappointed to see this committed still after the concerns
raised here.
- Jon
On Sat, Jun 12, 2010 at 6:24 AM, Pierre Joye pierre@gmail.com wrote:
hi Ilia,
So you basically say that the worries and wishes raised here are
simply irrelevant and at the end of the day you decide
Hello !
Is it just me or are we missing a way in the language to check if a
variable
that has been set to NULL exists or not?
is_null() on an unset variable throws a NOTICE.
$var === null throws a notice.
So, you have to use isset()? But, ah,
$var = null;
if(isset($var))
yields false.
Is
The concerns you raised about custom methods specific to database drivers
were not reflective of the PDO's intent as was clarified by Wez and myself.
The code that was introduced was specific to PostgreSQL, the common
functionality was introduced in a way that allows each driver to implement.
On
On 12.06.2010, at 15:54, Ilia Alshanetsky wrote:
The concerns you raised about custom methods specific to database drivers
were not reflective of the PDO's intent as was clarified by Wez and myself.
The code that was introduced was specific to PostgreSQL, the common
functionality was
hi Ilia,
Having bad design in the initial PDO implementation does not mean that
we have to continue to do it this way.
The concerns raised in this discussion are very valid. I do not see
nor understand the need to commit these additions at this stage. It
has been obvious that PDO needs
Hi Hannes:
On Fri, Jun 11, 2010 at 07:34:54PM +0200, Hannes Magnusson wrote:
Which part of zend_throw_exception() sounds like a php-general@ question?
DOH!
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
