bigint

Bulk copy into a table with bigint columns is not supported for Downlevel clients .

对于下级客户端，不支持向具有bigint列的表中进行大容量复制。

However , the resulting datatype from arithmetic computations using INTEGER / BIGINT versus DECIMAL must be considered when making this decision .

但是，当做这个决定时，必须将运算结果的数据类型考虑在内。

Note that this atomic domain is defined as DOUBLE , while the data type for the database column ( determined using reverse engineering ) is a BIGINT .

注意，这个原子域被定义为DOUBLE，而数据库列（由反向工程决定）的数据类型为BIGINT。

For processing efficiency and possible space savings , consideration should be given to replacing DECIMAL ( x , 0 ) data types with INTEGER or BIGINT .

为了提高处理效率和尽可能地节约空间，应该考虑用INTEGER或BIGINT代替DECIMAL（x，0）数据类型。

The table has a row change timestamp column : A ROW CHANGE TOKEN expression returns a BIGINT value derived from the timestamp value in the column .

表具有一个行修改时间戳列：ROWCHANGETOKEN表达式返回一个从列的时间戳值获得的BIGINT值。

You need to be careful and ensure that primary key , foreign key or index columns are declared as DECIMAL ( 31 ) or BIGINT in DB2 .

需要确保DB2中的主键、外键或索引列声明为DECIMAL（31）或BIGINT。

The table does not have a row change timestamp column : A ROW CHANGE TOKEN expression returns a derived BIGINT value that is shared by all rows located on the same page .

表没有定义行修改时间戳列：ROWCHANGETOKEN表达式返回一个派生的BIGINT值，由同一页面中的所有行共享。