Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78050 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64069 invoked from network); 14 Oct 2014 18:33:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2014 18:33:39 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.200 imap1-2.ox.privateemail.com Received: from [192.64.116.200] ([192.64.116.200:36721] helo=imap1-2.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A7/E0-18603-28C6D345 for ; Tue, 14 Oct 2014 14:33:39 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 7F698B00093; Tue, 14 Oct 2014 14:33:36 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap1.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap1.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id UJITCnpcOoxg; Tue, 14 Oct 2014 14:33:36 -0400 (EDT) Received: from [10.0.110.86] (border-converged.hackerdeen.org [89.104.225.218]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 8D87AB0008A; Tue, 14 Oct 2014 14:33:33 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: <543D6B9E.4000205@lsces.co.uk> Date: Tue, 14 Oct 2014 19:33:30 +0100 Cc: "internals@lists.php.net >> PHP internals" Content-Transfer-Encoding: quoted-printable Message-ID: <30774AB4-3546-4A13-96C6-B511C9F6E12E@ajf.me> References: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me> <543CE41B.5020308@sugarcrm.com> <543D5C78.9040905@sugarcrm.com> <543D61F3.3000000@lsces.co.uk> <543D6B9E.4000205@lsces.co.uk> To: Lester Caine X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] [RFC] Big Integer Support From: ajf@ajf.me (Andrea Faulds) On 14 Oct 2014, at 19:29, Lester Caine wrote: > If a 64bit build of PHP is using a simple integer key for a BIGINT key > from the database, what will be the equivalent on a 32bit build? >=20 > It may be that we have to add code to the DB drivers to ensure that > BIGINT remains a standard string conversion on both platforms in order > to maintain consistent results. One being a simple integer key and the > other a GMP based key IS a problem when the key is constructed from > other shifted elements. This may be no more complicated than happens > now, but is a real life situation that needs a consistent result. So, we=92re talking about array keys, right? Well, strings sometimes = become integer keys, and sometimes become string keys in arrays. This is = actually the same behaviour the RFC and patch currently have for = bigints: if it=92s in the range of a long, it=92s an integer key, = otherwise a string key. So the handling would actually be the same as now for array keys. -- Andrea Faulds http://ajf.me/