on 08-09-2008 7:30 PM
Hi all,
maybe this one is a silly question (if so sorry for that..), but as we are migrating a MaxDB 7.6 database from a Win32 to a Win64 server machine we came up with concerns if the datatypes - esp. INTEGER - were plattform independent; meaning: if INTEGER columns and variables in stored procedure/ triggers behave on a Win32 and WIn64 the same ?!
We studied the doc's which gave us the hint that INTEGER is in fact +/-2^31-1 (=Int32), but did not say a word about (express verbis) about this topic.
Thanks in advance!
Frank
Hi all,
the datatype integer or int in columns of database tables and in stored procedures is always (no matter if 64-bit machine or 32-bit one, no matter if Unix, Windows or whatsoever), always fixed(10) with an implicit constraint of being between -2GB and +2GB.
It has nothing to do with native (C++ or so) integer and its reliance on the used OS.
Elke
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
AFIAK Win64 is LP64 - means, longs and pointers are 64bit, int is still 32bit (LP64 vs. ILP64).
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Markus,
thanks for your reply!
That means INTEGER indeed stays 32bit on Win64 and keeps the same behaviour when used as datatype for table columns and stored procedures (background: the to be migrated database has a bunch of stored procedures that use INTEGER variables for calculations..)?
(I am asking just to be sure what to expect when we will run our test scenarios..)
kind regards
Frank
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.