Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Integer overflow in version 2?
Hi,
I have some integration tests in which I create a record in a certain table with the highest id possible (the type is NUMBER(12, 0) so I use 999999999999).
The problem I'm having is that with version 2 of the Node driver when reading the data it's overflowing somewhere, as I get 'ID: -727379969' in the query results. It's as if now the integers were 32 bit. This didn't happen to me in version 1. I've tried in both Linux and Mac (64 bit machines).
Is this a bug?
Thank you.
Answers
-
Please post a runnable example program plus table creation sql.
Please post input/output of the program showing the "error
Please also supply db version (4 digits), client and server OS version and architecture.
Any other information that may beuseful to re-create what you are seeing and doing.
-
Can you post at https://github.com/oracle/node-oracledb/issues and include the info that @Gaz in Oz requested?
-
Done, thank you. https://github.com/oracle/node-oracledb/issues/833
-
A general note to people reading this thread: Node.js's number range is limited so you may need to fetch numbers as strings and use a 3rd party module such as bigint to handle them 'properly'. Some details are in https://github.com/oracle/node-oracledb/issues/842 . Perhaps a better general recommendation is to do all number calculations in SQL or PL/SQL.
-
node-oracledb 2.1 is out with the specific regression fixed. My earlier comments about Node.js's number range still apply, of course.
