How to avoid trailing zero (after decimal point) for numeric typecolumn - Mailing list pgsql-general

From pkashimalla
Subject How to avoid trailing zero (after decimal point) for numeric typecolumn
Date
Msg-id 1519821226862-0.post@n3.nabble.com
Whole thread Raw
Responses Re: How to avoid trailing zero (after decimal point) for numeric type column
Re: How to avoid trailing zero (after decimal point) for numeric type column
List pgsql-general
Hello Team,

We have recently migrated our database from Oracle
And there are few of my tables with numeric column type.

In below example
I did insertion from java program with below code snippet

Double object = 10.0;
String inserRecordQuery_NEWWAY11 = "INSERT INTO BLOB_TEST_TABLE(id)VALUES
(?)";
selectPrepareStmt.setObject(1, object,Types.NUMERIC);
int count = selectPrepareStmt.executeUpdate();

it inserted like this.
/
select id from blob_test_table;

id
numeric
-------------
10.0/


In this case, when a decimal point is equal to 0 then,  I don't want to see
the precision and the value in the column should just 10

And If I execute code,

Double object = 10.5801
String inserRecordQuery_NEWWAY11 = "INSERT INTO BLOB_TEST_TABLE(id)VALUES
(?)";
selectPrepareStmt.setObject(1, object,Types.NUMERIC);
int count = selectPrepareStmt.executeUpdate();

Now ,the value in the column should be 10.5801 as the precision is greater
than ZERO

Because of this, the migrated data (from Oracle) is without PRECISION ZERO
and the new data which is being inserted is with PRECISION ZERO. 

/
select id from blob_test_table;

id
numeric
-------------
10.0
10
11
11.0
/

Is there a possible setting in PostgreSQL server to achieve this?

FYI - 

Oracle's NUMBER column type is handling it as I expected.
I migrate Oracle's NUMBER column as just NUMERIC column in PostgreSQL



Thanks,
Praveen




--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html


pgsql-general by date:

Previous
From: mariusz
Date:
Subject: Re: Given a set of daterange, finding the continuous range thatincludes a particular date (aggregates)
Next
From: Jeremy Finzel
Date:
Subject: Enforce primary key on every table during dev?