Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98776 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17950 invoked from network); 12 Apr 2017 15:22:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Apr 2017 15:22:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=adam.baratz@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=adambaratz@php.net; sender-id=unknown Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.175 as permitted sender) X-PHP-List-Original-Sender: adam.baratz@gmail.com X-Host-Fingerprint: 209.85.216.175 mail-qt0-f175.google.com Received: from [209.85.216.175] ([209.85.216.175:33522] helo=mail-qt0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/69-18853-B164EE85 for ; Wed, 12 Apr 2017 11:22:03 -0400 Received: by mail-qt0-f175.google.com with SMTP id m36so24897552qtb.0 for ; Wed, 12 Apr 2017 08:22:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DxK/JaSGkKot8XxJRJa4S3TfF2LnzNbo3vfcLJT0Ae0=; b=hvt1pGGdo5PsL9vWqJQ29R7zIawixgAmSMKbQQ9XQ3Dh2gPsms1Bqe1zYhJTNWSuFc qM+w4te71Nq0q8CDY+JVlyOyajyYkBf2179tcHfF1Jn7S6McMk2qHW1KeHPvPy0ts4aY NQCJPR230ob/WKjGJjecds+7XpaIMwmoyb/GiGZxebR8/i2HQyppd57XlDFJBw/v4V+j 041VK0+zplddP+R+hb5rdf5Gkfxy6QpkX0FPwv277Mnd41GLOLwvJPG5fl/Zx6izHxy9 0Fs8mNaTn4Pu89HzXtrKdDVl1iZGxlpjYOpyvj3vbYDYh+D8WlZbDkJzAoMkEvlWBdMl qAfQ== X-Gm-Message-State: AN3rC/6/oqO9aqjH+QtBHVWpZNlF5L8tvH9BHa/dKzBHWnhsuSv52Y7sOYaeygcWHZ343A== X-Received: by 10.200.56.51 with SMTP id q48mr4141118qtb.83.1492010520475; Wed, 12 Apr 2017 08:22:00 -0700 (PDT) Received: from mail-qt0-f170.google.com (mail-qt0-f170.google.com. [209.85.216.170]) by smtp.gmail.com with ESMTPSA id n195sm8382957qke.28.2017.04.12.08.21.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Apr 2017 08:21:59 -0700 (PDT) Received: by mail-qt0-f170.google.com with SMTP id c45so24830613qtb.1 for ; Wed, 12 Apr 2017 08:21:59 -0700 (PDT) X-Received: by 10.200.40.72 with SMTP id 8mr3386393qtr.204.1492010519155; Wed, 12 Apr 2017 08:21:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.135.212 with HTTP; Wed, 12 Apr 2017 08:21:58 -0700 (PDT) In-Reply-To: <8923084a-a357-91e9-44b5-52a4af0a5df1@beccati.com> References: <5e3e3e9b-f5b9-a19e-c4cb-6af0f5985d94@beccati.com> <8923084a-a357-91e9-44b5-52a4af0a5df1@beccati.com> Date: Wed, 12 Apr 2017 11:21:58 -0400 X-Gmail-Original-Message-ID: Message-ID: To: Matteo Beccati Cc: "internals@lists.php.net" , Andrea Faulds Content-Type: multipart/alternative; boundary=001a11410c64fee17a054cf9c4f2 Subject: Re: [PHP-DEV] [RFC] PDO Float Type From: adambaratz@php.net (Adam Baratz) --001a11410c64fee17a054cf9c4f2 Content-Type: text/plain; charset=UTF-8 > > > I'd suggest adding a warning to the manual instead. > > I think that's a requirement in any case. I'd be most comfortable with this approach. I'd worry about adding a PDO::PARAM_NUMERIC type without investigating how it needs to function for each DB, which feels like scope creep. If it starts off as an alias for PDO::PARAM_STR, there could be issues updating it to work correctly, especially if the right design involves modeling the precision somewhere. I added a "Future Scope" section covering this. Let me know if there are major problems with this or other points to cover. Otherwise, I'll aim to open voting on Monday. Thanks, Adam --001a11410c64fee17a054cf9c4f2--