Re: What is wrong with this code?
| From: | Thijs Lensselink | Date: | Wed, 28 Apr 2010 12:17:47 +0000 |
| Subject: | Re: What is wrong with this code? | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-304717@lists.php.net to get a copy of this message | ||
Gary . wrote:
On 4/28/10, Thijs Lensselink wrote:Yes, or something very like it. See Message-ID: <y2la35643581004280018i22b3de1ag1a836e7229378b77@mail.gmail.com> That message is about defining the class constant. Which is done. But later on it is called as a normal constant. Not a class constant Besides the fact that it should throw a notice. It also makes sure Pg_Error::$errors looks a bit different then expected array(1) { ["INTEGRITY_CONST_UNIQUE"]=> string(30) "uniqueness constraint violated" } This makes Pg_Error::getMessage(23505) always return string(0)"" which equals false....Gary . wrote:Shouldn't this be: array(self::INTEGRITY_CONST_UNIQUE => 'uniqueness constraint violated');{class Pg_Errorprivate static $errors = array(INTEGRITY_CONST_UNIQUE => 'uniqueness constraint violated');