Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:31381 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99158 invoked by uid 1010); 2 Aug 2007 17:33:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 99143 invoked from network); 2 Aug 2007 17:33:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Aug 2007 17:33:02 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.136 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 213.123.20.136 c2bthomr04.btconnect.com Received: from [213.123.20.136] ([213.123.20.136:25455] helo=c2bthomr04.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 42/69-35404-94512B64 for ; Thu, 02 Aug 2007 13:33:00 -0400 Received: from [127.0.0.1] (host81-138-11-136.in-addr.btopenworld.com [81.138.11.136]) by c2bthomr04.btconnect.com with ESMTP id HJB26977; Thu, 2 Aug 2007 18:31:57 +0100 (BST) Message-ID: <46B21554.4070906@lsces.co.uk> Date: Thu, 02 Aug 2007 18:33:08 +0100 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.5) Gecko/20070716 SeaMonkey/1.1.3 MIME-Version: 1.0 To: PHP Developers Mailing List Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: php_interbase problems From: lester@lsces.co.uk (Lester Caine) OK I've finally spent time working through the problems of getting PHP5.2.x working with my legacy applications, and after a lot of dead ends I've finally tracked one problem down to the php_interbase module not returning the right thing for a blob_id - giving '0x %i' instead. I suspect that this was broken between 5.1.6 and 5.2.0 but I'm currently working with 5.2.3. So is this a problem that has popped up in other modules and just needs a quick tweak, or do we have to start panicking and dig deep in php_interbase code? -- Lester Caine - G8HFL ----------------------------- Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact L.S.Caine Electronic Services - http://home.lsces.co.uk MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/ Firebird - http://www.firebirdsql.org/index.php