Bug #80445 [Com]: Using float bind parameter returns weird error

From: Date: Mon, 25 Jan 2021 05:25:31 +0000
Subject: Bug #80445 [Com]: Using float bind parameter returns weird error
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-231743@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=80445&edit=1 ID: 80445 Comment by: camillestewa at gmail dot com Reported by: domen at jollydeck dot com Summary: Using float bind parameter returns weird error Status: Re-Opened Type: Bug Package: PDO MySQL Operating System: Windows, CentOS PHP Version: 7.4.13 Block user comment: N Private report: N New Comment: Bind variables for the parameter markers in the SQL statement that was passed to mysqli_prepare(). Note Coming to the problem calling mysqli::bind_param() with a dynamic number of FLOAT/REAL/DOUBLE (PRECISION) should all be. https://www.prepaidcardstatus.bid/ Previous Comments: ------------------------------------------------------------------------ [2020-12-24 07:20:26] alexmorgan0559 at gmail dot com Hey Domen, I have been experiencing the same issue for quite some time. Taking php assignment help(https://www.assignmentdesk.co.uk/php-assignment-help) has resolved it for me, you could try the same. ------------------------------------------------------------------------ [2020-11-30 20:26:04] cmb@php.net Ah, okay, that makes sense. :) ------------------------------------------------------------------------ [2020-11-30 16:41:12] domen at jollydeck dot com MySQL bug: https://bugs.mysql.com/bug.php?id=101806 ------------------------------------------------------------------------ [2020-11-30 13:33:39] domen at jollydeck dot com Hi, I've stripped the original query of unnecessary stuff so that bug report could be as simple as possible and to avoid wasting your time. Real use case is this: we have a table of "weights" which influence some application logic. After each user action this weight is multiplied by some factor, rounded and limited to lower and upper bound. This could be achieved by retrieving value, doing calculations in PHP and then updating value in table, but "simple" expression GREATEST(LEAST(ROUND(field * ?), ?), ?) does the job and also avoids any table locking that is needed between retrieving and updating the value. I've put word "simple" in quotes because expression has now become GREATEST(LEAST(ROUND(field * CAST(? AS FLOAT)), CAST(? AS UNSIGNED)), CAST(? AS UNSIGNED)) so that is works with stringified numeric bound parameters. I know PDO::PARAM_INT exists, but this is legacy application. ------------------------------------------------------------------------ [2020-11-30 13:13:02] cmb@php.net > $pdo->query("CREATE TABLE test > (field INT NOT NULL) ENGINE=InnoDB"); > $stmt = $pdo->prepare("UPDATE test SET > field = 100 * ?"); This looks plain wrong to me. Why don't you do the calculation in PHP, and send an integer in the first place? And if it is about monetary calculations with floats, you likely have bigger issues than this query[1]. [1] <http://www.floating-point-gui.de/> ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=80445 -- Edit this bug report at https://bugs.php.net/bug.php?id=80445&edit=1

« previous php.bugs (#231743) next »