Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58216
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
Received-SPF: pass (google.com: domain of keisial@gmail.com designates 10.180.107.162 as permitted sender) client-ip=10.180.107.162;
Message-ID: <4F4C0FF2.70507@gmail.com>
Date: Tue, 28 Feb 2012 00:21:22 +0100
User-Agent: Thunderbird
MIME-Version: 1.0
To: Richard Lynch <ceo@l-i-e.com>
CC: internals@lists.php.net
References: <CAG=uTXFQUY=EDb=ut97nNSm+m8sMQNRK-9YPcfb2quaoS246-g@mail.gmail.com>    <CAAyV7nHA_DhyZUqU2=EYDSvCEYmc7MFejsG97dXCoTtaeMurMg@mail.gmail.com>    <4F4686C6.2040207@sugarcrm.com>    <CAKOpQSwtHvSoSVj8q4_QTte42D588OUBDBQ_a4YB8q=GquekBQ@mail.gmail.com>    <fe9c203ff43ec075a6f1a405053889ec.squirrel@www.l-i-e.com>    <CAKOpQSwqddd1YUeuTGOQWX+V9SA_is-2UE1TOXfqt1YQoz2upw@mail.gmail.com>    <CAG=uTXGTCxaEEOdt7cz81DT7vOOvMm1P0jdrgMX0CpY4e86t+Q@mail.gmail.com>    <CAKOpQSy7r063FuoXpAy_7nsaBpz08LrVnz0zpa6CDF7fF-Tu6g@mail.gmail.com>    <4F496818.8000405@sugarcrm.com>    <CAKOpQSyewRGH8nZhXAZf9+hh1pU1oNGfZCn5rbfPW8Ydy9aH9g@mail.gmail.com>    <4F4982BF.8090102@sugarcrm.com>    <CAKOpQSwo0xy4tyZQW6zZGeuZgqCEGEqUpbD=iAWfa4TkaeeqrQ@mail.gmail.com>    <CAL0xaBFwbmamuNCuakxv9jf2LXQQ4ej4RvFRm_UBD460Sazprg@mail.gmail.com>    <4F4AA569.10502@gmail.com>    <CAKOpQSz5vCXDr0Ms8HSD=5BXwuUxpnauc8QKXGAKYhC6cnpEEg@mail.gmail.com> <6d7e3ff8878174e4ae627b6744744330.squirrel@www.l-i-e.com>
In-Reply-To: <6d7e3ff8878174e4ae627b6744744330.squirrel@www.l-i-e.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Enum proposal (yet another)
From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=)

On 27/02/12 19:22, Richard Lynch wrote:
>>> I'm not so sure about that. In a well-written web application, you
>>> would
>>> typically convert them on the first layer, when receiving from the
>>> web.
>>> On next usages, your int variables are usually ints already.
> Afraid not.
>
> It turns out that PHP, on 32-bit hardware, converting large BIGINT
> using (int) $ID ends up as a negative number, and then when you pass
> it in to the database if a string query, you get a negative ID, not at
> all what was intended.
>
> (Been there, done that, got burned)
>
> At least, that's been my experience with some versions of PHP and some
> database drivers.
>
> So at least the database IDs have to remain as strings, if you are
> using BIGINT.
>
> You could, of course, only convert the values known to be in range of
> PHPs positive integers, and leave the others as strings.
>
> This is just a simple example of how the super strict typing simply
> doesn't work out too well in PHP.
That's a good example from experience.
Although if you want to keep ids as strings, you can simply keep them as a
string type.
I was thinking on input coming from a web browser, btw.