1
 Follower
17
 Likes

Support for BIGINT datatype (SQL Server)

Database
Implemented
on 01 Oct 2015
OutSystems 9.1

Support for BIGINT datatype (SQL Server)

Created on 15 Nov 2010
Comments (6)
Care to explain why?

Is Decimal not good enough for the cases the OS integer is not enough?
Reason:
 
INT (default) primary key used by outsystems.
Range: -2,147,483,648 to 2,147,483,647
Storage: 4 Bytes
 
BIGINT (not supported by outsystems)
Range: -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807
Storage: 8 Bytes

DECIMAL To get the equivalent range of BIGINT in decimal, you would need a precision of 19 and a scale of 0. ie DECIMAL(19,0), this will now support the BIGINT range, but with a greater range.
 
However DECIMAL with a precision greater or equal to 10 uses up 9 bytes of storage, unlike bigint which uses 8 bytes of storage, therefore the difference here is that DECIMAL(19,0) uses 1 extra byte per value stored.
 
Reference
https://msdn.microsoft.com/en-us/library/ms187745.aspx
https://msdn.microsoft.com/en-us/library/ms187746.aspx
Outsystems confirmed support for BIGINT.

"It is in our backlog, but word from our Product Management is that we are indeed planning to support bigint as an identifier in the future, but unfortunately there isn’t a date for it yet."

Paulo Tavares (10th of December 2010)
Merged this idea with 'Support for more Database Datatypes' (created on 2011-03-30 14:28:12 by Eric Oud Ammerveld (PS10))
Currently i.e. Large / Bigint is unsupported.
It would be nice if these were to be added as a datatype.

Merged from 'Support for more Database Datatypes' (idea created on 2011-03-30 14:28:12 by Eric Oud Ammerveld), on 2011-04-07 08:59:59 by Rodrigo Castelo

Thank you for the feedback and context.

Long Integers is available in OutSystems 9.1 Bali. Enjoy

views
1059
Followers
1