Eiffel: ODBC处理BIGINT

Question

埃菲尔铁塔

看起来我得到了一个来自使用Eiffel DB_SELECTION.cursor的ODBC的BIGINT的INTEGER_32_REF。有时我看起来很有价值，但有时却没有。

946383958 => good INTEGER_32_REF (id->4 of following table)
9475984837 => 886050245 WRONG INTEGER_32_REF (id->4 of following table)

646383958 => good INTEGER_32_REF (id->3 of following table)
6475984837 => -2113949755 WRONG INTEGER_32_REF (id->4 of following table)

...

它的行为看起来就像不处理BIGINT值，而是直接从DB值解释INTEGER_32_REF值，典型的情况是传递2^32

Postgresql

将包含以下数据的表作为electricity_amount BIGINT NOT NULL DEFAULT 0

id |   a_date   |  amount   | electricity_amount | consumption_sector_id | electricity_rate_id
----+------------+-----------+--------------------+-----------------------+---------------------
1 | 2019-01-01 | 746383958 |         7475984837 |                     1 |                   1
2 | 2019-02-01 | 846383958 |         8475984837 |                     1 |                   1
3 | 2019-03-01 | 646383958 |         6475984837 |                     1 |                   1
4 | 2019-04-01 | 946383958 |         9475984837 |                     1 |                   1

​

​

Answer 1

默认情况下，并非所有数据类型都映射到Eiffel侧。因此，您将需要从GLOBAL_SETTINGS类继承并将该功能称为set_use_extended_types (True) --| Use extended types: INTEGER_64, STRING_32 etc.