BigInt vs Int in SQL Server

robv

Any reason why AwareIm uses BIGINT field data type for reference _RID fields but an INT field data type for the ID field.

The subtle difference causes a data type mismatch when using a third party report tool when linking the data in related tables.

(Please note: This question is specific to SQL Server. This situation did not arise with MySQL.)

aware_support

The only reason is that ID fields are represented as "long" in Java. The SQL Server driver translates these to BIGINT, so it's really a driver doing, not Aware IM's.

The reporting tool could be smarter and not cause a data mismatch for such compatible types.