Skip to main content

Usage of Float,Double and Decimal Data Types in MySql

When we start developing a database, we have to use the most appropriate data types for all the columns to store data values of the respective tables in it. For dealing with the floating type data values, most of the times, we get confused about which data type to go for, as we have Float, Decimal and Double as well.

I, myself, as a new DBA, got confused about the usage of the same. So, i have re-searched through some websites over internet and have concluded some facts about these data types' usage. i want to share my experience with all of you.



  • FLOAT : When we use this data type, it considers only 4 digits which are entered after decimal and ignores the other digits afterwards.
for example,

create table myTable(marks float);
insert into myTable values(25.54675);

When we will execute these queries, a table will be created "myTable" with a column "marks" having a value "25.5467".

  • Double : When we use this data type, it considers only 14 digits which are entered after decimal and ignores the other digits afterwards.
for example,

create table myTable(marks double);
insert into myTable values(21.97653876235671234);

When we will execute these queries, a table will be created "myTable" with a column "marks" having a value "21.97653876235671”.

  • Decimal : When we use this data type, it considers only 1 digit entered after decimal and ignores the other digits afterwards.
for example,

create table myTable(marks decimal);
insert into myTable2 values(23.274);

When we will execute these queries, a table will be created "myTable" with a column "marks" having a value "23”.

This is the case in which the digits after decimal point is less than 5.

Same ways, if we perform the below query,

create table myTable(marks decimal);
insert into myTable2 values(23.518);

We can notice that, if the digits after the decimal point are greater than or equal to 5, then, the digit before decimal point is incremented.


Happy Reading
Gunjan Singh - Facebook

Comments

Popular posts from this blog

How to encrypt and decrypt Table data in postgres

For encrypting and decrypting , we must use the bytea data type on the column which we implement. Bcoz bytea will use the pgcrypto method by default. However, you will need to create the pgcrypto extension to enable these functions as they are not pre-defined in PostgreSQL/PPAS. Example CREATE EXTENSION pgcrypto; CREATE TABLE userinfo (username varchar(20), password bytea); >>    Inserting the data in an encrypted format INSERT INTO userinfo VALUES(' suman ',encrypt('111222','password','aes')); select * from userinfo ; >>    Retrieving the data as decrypted format SELECT decrypt(password,decode('password','escape'::text),'aes'::text) FROM userinfo; Thanks for reading Plz dont forget to like Facebook Page.. https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

How to recover msdb database from suspect mode

 It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element xx.xxx.xx:function .dbo.xxx has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally