Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86077
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.51 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <CAL0xaBGx_JYuduoAFAoNKNWOa8JXtUi5hJnaNR1_c3eFYg8NkQ@mail.gmail.com>
References: <CAGa2bXYzp3XimLXxC+Py2t1DWhCfX8coTdYHzf6zEiKdxA7r8Q@mail.gmail.com>
 <55401F31.9030703@gmail.com> <CAObuZduZBM0GyWJMA1Fd7eCgPE4vFFZrrhpREQ50a4QJhG6Nvg@mail.gmail.com>
 <CAGa2bXar_oXrsPAErNx5BUdkFAy-p8-D0tfhc3pAnDTGBGJJ7Q@mail.gmail.com>
 <55416849.9010808@gmail.com> <CAGa2bXbkCx2Nqb9YBut3id4N=nhjLBGPN8Ucrx7R6mRnGjB2og@mail.gmail.com>
 <5541753D.5050908@gmail.com> <CAGa2bXYk=2TVFv9aeDjVRpgLKFjhYx6YBCpmWo10u-Qv8b0zpg@mail.gmail.com>
 <55419C0C.7020207@gmail.com> <CAGa2bXaPAwFs=2=wHAE615dhyFO_5sUnKV4X2cMVFJM9xoG1wg@mail.gmail.com>
 <5541C0E0.2080006@gmail.com> <CAMPTd_AK8sr2EVH38wWmv1LzRp1=ShA2uNon=+cPYukwDUG2LA@mail.gmail.com>
 <CAL0xaBGx_JYuduoAFAoNKNWOa8JXtUi5hJnaNR1_c3eFYg8NkQ@mail.gmail.com>
Date: Thu, 30 Apr 2015 15:54:18 +0900
Message-ID: <CAGa2bXZ5rd0-4bnKNtSyjxso=8K=MyZsULBLby-5+TgfVk6Y0A@mail.gmail.com>
To: Arvids Godjuks <arvids.godjuks@gmail.com>
Cc: Walter Parker <walterp@gmail.com>, Stanislav Malyshev <smalyshev@gmail.com>, 
	Ryan Pallas <derokorian@gmail.com>, "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0111d7caf9ada30514eb92c7
Subject: Re: [PHP-DEV] Adding "numeric" type hint
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e0111d7caf9ada30514eb92c7
Content-Type: text/plain; charset=UTF-8

Hi Arvids,

On Thu, Apr 30, 2015 at 3:40 PM, Arvids Godjuks <arvids.godjuks@gmail.com>
wrote:

> Stop trying to fix clever idiots from shooting themselves in the foot. The
>> standard result from these actions is to make life a pain for regular or
>> better programmers while only adding mild speed bumps to those clever
>> idiots.
>>
>> Things like a numeric type will only encourage the clever idiots to write
>> half broken code.
>>
>
> Hello, just want to chip in.
>
> I use "INT UNSIGNED" for the MySQL primary keys since ages, because
> negative primary keys make no sense. Well, mostly ID's for the records
> actually can stay strings, but I will have to remember to use a string type
> hint every time I pass a record ID. I expect a lot of times to forget that
> and write int...
> I was bitten a few times by the limits of 32 bit integer sizes too (moved
> to a 64 bit server that time), but there are also unsigned 64 bit integers
> that can and will be used in math operations and passed around. And we
> don't have the "unsigned int".
>

Use of unsigned int8 for ID makes sense almost always if database supports
it.
I may do such mistake even if I know I should use "string" (or "numeric")
for record IDs once I
start using type hints.

Okay, we have GMP. I will have to use it. But let me just ask - if I work
> with a DB handling 64 bit integers (all I know handle them) or use a
> DECIMAL field - automaticly use GMP then? Oh gosh....
>

I'm planning to introduce type affinity like SQLite. Then appropriate types
for the value may
be used automatically/semi-automatically. It's good for both security and
performance.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e0111d7caf9ada30514eb92c7--