Re: store numeric numbers with plus minus signs

On 4/14/2023 4:22 PM, [email protected] wrote:
> I didn't find this topic in the discussion history ... wonder what's the best practice in MySQL to store numeric numbers with plus minus signs (+/-), times sign such as in 2.328x10-15, such that they can be safely stored, easily handled/recognized by most current programs in perl/php/etc and
> shown in modern web browsers.
> 
> My problem came from a practice developing a MySQL database since 20 years ago, when such numeric numbers are copied/pasted into MySQL via web forms and displayed well on web when retrieved back then. However in the following years these old data were started to be shown as with black
> diamond squares or other types of partial-garbaged number.
> 
> Over 10+ years ago when these strange character showed up I can doggle for different character coding methods in a browser to view them. But nowadays all browsers are made "smart" as no longer
> to provide these user options.
> 
> I understand this came along with different/evolving char coding methods; and the data we curated into the database over different times in history were with changing character (or language) settings. I wonder is there a good solution to bring them all to a current character safe environment, and kept safe for the future?
> 
> j


The SQL standard states a plus sign is optional whereas a minus sign is 
required for negative numbers.  Addtionally, the times sign is not 
allowed.  Instead, "E" is used, as in 2.328E-15.

This is standard in many programming languages, also.

And of course you store numeric values in a numeric type column.

Also, NEVER copy/paste from a web form when working with ANY database. 
ALWAYS validate the information before inserting to prevent SQL 
injection exploits.

-- 
==================
Remove the "x"'s from my email address
Jerry Stuckle
[email protected]
==================