Correct column types in Oracle and PostgreSQL for Java(Hibernate) Float type
I need create column for storage Float value in Oracle and PostgreSQL.
@Column(name = "SOME_VALUE")
private Float someValue;
How do I create columns in both bases so that Hibernate is mapping normally?
I tried the FLOAT type in Oracle (and it work) and BIGINT in PostgresSQL.
But I am confused by my choice. I want the most correct types for both databases.
java oracle postgresql hibernate
edited Dec 7 '18 at 16:30
Cœur
18.1k9108148
asked Nov 14 '18 at 10:35
ip696ip696
1,24321238
add a comment |
I need create column for storage Float value in Oracle and PostgreSQL.
@Column(name = "SOME_VALUE")
private Float someValue;
How do I create columns in both bases so that Hibernate is mapping normally?
I tried the FLOAT type in Oracle (and it work) and BIGINT in PostgresSQL.
But I am confused by my choice. I want the most correct types for both databases.
java oracle postgresql hibernate
edited Dec 7 '18 at 16:30
Cœur
18.1k9108148
asked Nov 14 '18 at 10:35
ip696ip696
1,24321238
add a comment |
I need create column for storage Float value in Oracle and PostgreSQL.
@Column(name = "SOME_VALUE")
private Float someValue;
How do I create columns in both bases so that Hibernate is mapping normally?
I tried the FLOAT type in Oracle (and it work) and BIGINT in PostgresSQL.
But I am confused by my choice. I want the most correct types for both databases.
java oracle postgresql hibernate
edited Dec 7 '18 at 16:30
Cœur
18.1k9108148
asked Nov 14 '18 at 10:35
ip696ip696
1,24321238
I need create column for storage Float value in Oracle and PostgreSQL.
@Column(name = "SOME_VALUE")
private Float someValue;
How do I create columns in both bases so that Hibernate is mapping normally?
I tried the FLOAT type in Oracle (and it work) and BIGINT in PostgresSQL.
But I am confused by my choice. I want the most correct types for both databases.
java oracle postgresql hibernate
java oracle postgresql hibernate
edited Dec 7 '18 at 16:30
Cœur
18.1k9108148
asked Nov 14 '18 at 10:35
ip696ip696
1,24321238
edited Dec 7 '18 at 16:30
Cœur
18.1k9108148
asked Nov 14 '18 at 10:35
ip696ip696
1,24321238
edited Dec 7 '18 at 16:30
Cœur
18.1k9108148
edited Dec 7 '18 at 16:30
Cœur
18.1k9108148
edited Dec 7 '18 at 16:30
Cœur
18.1k9108148
18.1k9108148
asked Nov 14 '18 at 10:35
ip696ip696
1,24321238
asked Nov 14 '18 at 10:35
ip696ip696
1,24321238
asked Nov 14 '18 at 10:35
ip696ip696
1,24321238
1,24321238
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
For Oracle:
use NUMBER for arbitrary precision (if you can't afford rounding errors, for example with money) or BINARY_DOUBLE for faster processing, if rounding errors don't matter so much, like a temperature measurement.
For PostgreSQL:
The corresponding data types in PostgreSQL would be numeric and double precision.
FLOAT in Oracle is the same as NUMBER with a precision limit in binary digits, and bigint in PostgresSQL is for large integer numbers.
answered Nov 14 '18 at 11:09
Laurenz AlbeLaurenz Albe
47k102748
I use REAL for bouth bases. When I run script inoraclewas createdfloat(63)and inpostgres-real. Is it wrong or has the right to exist?
– ip696
Nov 14 '18 at 11:15
Those are also ok. As I wrote,FLOATis the same asNUMBERin Oracle, andrealis likedouble precision, except with fewer significant digits.
– Laurenz Albe
Nov 14 '18 at 11:19
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298166%2fcorrect-column-types-in-oracle-and-postgresql-for-javahibernate-float-type%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
For Oracle:
use NUMBER for arbitrary precision (if you can't afford rounding errors, for example with money) or BINARY_DOUBLE for faster processing, if rounding errors don't matter so much, like a temperature measurement.
For PostgreSQL:
The corresponding data types in PostgreSQL would be numeric and double precision.
FLOAT in Oracle is the same as NUMBER with a precision limit in binary digits, and bigint in PostgresSQL is for large integer numbers.
answered Nov 14 '18 at 11:09
Laurenz AlbeLaurenz Albe
47k102748
I use REAL for bouth bases. When I run script inoraclewas createdfloat(63)and inpostgres-real. Is it wrong or has the right to exist?
– ip696
Nov 14 '18 at 11:15
Those are also ok. As I wrote,FLOATis the same asNUMBERin Oracle, andrealis likedouble precision, except with fewer significant digits.
– Laurenz Albe
Nov 14 '18 at 11:19
add a comment |
For Oracle:
use NUMBER for arbitrary precision (if you can't afford rounding errors, for example with money) or BINARY_DOUBLE for faster processing, if rounding errors don't matter so much, like a temperature measurement.
For PostgreSQL:
The corresponding data types in PostgreSQL would be numeric and double precision.
FLOAT in Oracle is the same as NUMBER with a precision limit in binary digits, and bigint in PostgresSQL is for large integer numbers.
answered Nov 14 '18 at 11:09
Laurenz AlbeLaurenz Albe
47k102748
I use REAL for bouth bases. When I run script inoraclewas createdfloat(63)and inpostgres-real. Is it wrong or has the right to exist?
– ip696
Nov 14 '18 at 11:15
Those are also ok. As I wrote,FLOATis the same asNUMBERin Oracle, andrealis likedouble precision, except with fewer significant digits.
– Laurenz Albe
Nov 14 '18 at 11:19
add a comment |
For Oracle:
use NUMBER for arbitrary precision (if you can't afford rounding errors, for example with money) or BINARY_DOUBLE for faster processing, if rounding errors don't matter so much, like a temperature measurement.
For PostgreSQL:
The corresponding data types in PostgreSQL would be numeric and double precision.
FLOAT in Oracle is the same as NUMBER with a precision limit in binary digits, and bigint in PostgresSQL is for large integer numbers.
answered Nov 14 '18 at 11:09
Laurenz AlbeLaurenz Albe
47k102748
For Oracle:
use NUMBER for arbitrary precision (if you can't afford rounding errors, for example with money) or BINARY_DOUBLE for faster processing, if rounding errors don't matter so much, like a temperature measurement.
For PostgreSQL:
The corresponding data types in PostgreSQL would be numeric and double precision.
FLOAT in Oracle is the same as NUMBER with a precision limit in binary digits, and bigint in PostgresSQL is for large integer numbers.
answered Nov 14 '18 at 11:09
Laurenz AlbeLaurenz Albe
47k102748
edited Nov 14 '18 at 11:15
answered Nov 14 '18 at 11:09
Laurenz AlbeLaurenz Albe
47k102748
answered Nov 14 '18 at 11:09
Laurenz AlbeLaurenz Albe
47k102748
answered Nov 14 '18 at 11:09
Laurenz AlbeLaurenz Albe
47k102748
47k102748
I use REAL for bouth bases. When I run script inoraclewas createdfloat(63)and inpostgres-real. Is it wrong or has the right to exist?
– ip696
Nov 14 '18 at 11:15
Those are also ok. As I wrote,FLOATis the same asNUMBERin Oracle, andrealis likedouble precision, except with fewer significant digits.
– Laurenz Albe
Nov 14 '18 at 11:19
add a comment |
I use REAL for bouth bases. When I run script inoraclewas createdfloat(63)and inpostgres-real. Is it wrong or has the right to exist?
– ip696
Nov 14 '18 at 11:15
Those are also ok. As I wrote,FLOATis the same asNUMBERin Oracle, andrealis likedouble precision, except with fewer significant digits.
– Laurenz Albe
Nov 14 '18 at 11:19
I use REAL for bouth bases. When I run script in
oracle was created float(63) and in postgres - real. Is it wrong or has the right to exist?– ip696
Nov 14 '18 at 11:15
I use REAL for bouth bases. When I run script in
oracle was created float(63) and in postgres - real. Is it wrong or has the right to exist?– ip696
Nov 14 '18 at 11:15
Those are also ok. As I wrote,
FLOAT is the same as NUMBER in Oracle, and real is like double precision, except with fewer significant digits.– Laurenz Albe
Nov 14 '18 at 11:19
Those are also ok. As I wrote,
FLOAT is the same as NUMBER in Oracle, and real is like double precision, except with fewer significant digits.– Laurenz Albe
Nov 14 '18 at 11:19
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298166%2fcorrect-column-types-in-oracle-and-postgresql-for-javahibernate-float-type%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
