Closed GoogleCodeExporter closed 8 years ago
I am having a look here:
http://spain.angloinfo.com/money/banking/numerical-formats-standards/. It
appears that the format in the SQL is correct, but that the DB does not
understand it?
Original comment by nfranc...@gmail.com
on 26 Oct 2013 at 8:28
When SilverStripe convert the number 1.4492 to a string with
mysqli::real_escape_string (MySQLDatabase.php) put a comma instead of a point.
This causes that the SQL statement considered the number 1,4492 two
values, which produces the error. Apparently this is an error of
SilverStripe.
What do you think?
Regards,
Jose A.
Original comment by supp...@sendasoft.com
on 26 Oct 2013 at 6:55
"When SilverStripe convert the number 1.4492 to a string with
mysqli::real_escape_string (MySQLDatabase.php) put a comma instead of a point.
This causes that the SQL statement considered the number 1,4492 two
values, which produces the error. Apparently this is an error of
SilverStripe."
can you prove this? If so, we need to raise a ticket with SS. Let me know.
The error could also be within ecommerce, inserting the wrong value into the
SQL statement. Let me know.
Nicolaas
Original comment by nfranc...@gmail.com
on 27 Oct 2013 at 4:53
I have opened a ticket in silverstripe-framework.
From what I've researched the problem is in the function addslashes
(MySQLDatabase.php)
I give more details at this link.
https://github.com/silverstripe/silverstripe-framework/issues/2606
Please check it to see if it is correct.
Thanks,
Regards,
Jose A.
Original comment by supp...@sendasoft.com
on 27 Oct 2013 at 7:40
Now this works fine.
Nicolaas What have you done?
Was it a problem of ecommerce module?
Thanks,
Regards,
Jose A.
Original comment by supp...@sendasoft.com
on 28 Oct 2013 at 1:42
No, sorry, I was wrong.
This problem is not solved yet. :(
Regards,
Jose A.
Original comment by supp...@sendasoft.com
on 28 Oct 2013 at 1:52
Waiting on Jose. I think this is part of e-commerce and should be fixed ASAP!
Original comment by nfranc...@gmail.com
on 29 Oct 2013 at 2:01
This problem is because the silverstripe-fluent module uses setlocale(LC_ALL,
$locale).
Apparently the framework is not well prepared for changes of locale using this
function.
It's something that should solve silverstripe.
Definitely, the framework does not work properly when using this function.
If the ecommerce module generates SQL statements can be also affected by this
function.
https://github.com/silverstripe/silverstripe-framework/issues/2606
Regards,
Jose A.
Original comment by supp...@sendasoft.com
on 29 Oct 2013 at 6:58
This is a silverstripe wide issue... Lets hope it is solved soon.
https://github.com/silverstripe/silverstripe-framework/issues/2606
Original comment by nfranc...@gmail.com
on 26 Apr 2014 at 9:59
Original issue reported on code.google.com by
supp...@sendasoft.com
on 24 Oct 2013 at 6:32