Member walleye doesn't like this, since there is a separate .stdout file
for MinGW32. Will fix.
--
John Naylor
EDB: http://www.enterprisedb.com
Fix range check in ECPG numeric to int conversion
The previous coding guarded against -INT_MAX instead of INT_MIN,
leading to -2147483648 being rejected as out of range.
Per bug #17128 from Kevin Sweet
Discussion:
https://www.postgresql.org/message-id/flat/17128-55a8a879727a3e3a%40postgresql.or
Fix range check in ECPG numeric to int conversion
The previous coding guarded against -INT_MAX instead of INT_MIN,
leading to -2147483648 being rejected as out of range.
Per bug #17128 from Kevin Sweet
Discussion:
https://www.postgresql.org/message-id/flat/17128-55a8a879727a3e3a%40postgresql.or
Fix range check in ECPG numeric to int conversion
The previous coding guarded against -INT_MAX instead of INT_MIN,
leading to -2147483648 being rejected as out of range.
Per bug #17128 from Kevin Sweet
Discussion:
https://www.postgresql.org/message-id/flat/17128-55a8a879727a3e3a%40postgresql.or
Fix range check in ECPG numeric to int conversion
The previous coding guarded against -INT_MAX instead of INT_MIN,
leading to -2147483648 being rejected as out of range.
Per bug #17128 from Kevin Sweet
Discussion:
https://www.postgresql.org/message-id/flat/17128-55a8a879727a3e3a%40postgresql.or
Fix range check in ECPG numeric to int conversion
The previous coding guarded against -INT_MAX instead of INT_MIN,
leading to -2147483648 being rejected as out of range.
Per bug #17128 from Kevin Sweet
Discussion:
https://www.postgresql.org/message-id/flat/17128-55a8a879727a3e3a%40postgresql.or
Fix range check in ECPG numeric to int conversion
The previous coding guarded against -INT_MAX instead of INT_MIN,
leading to -2147483648 being rejected as out of range.
Per bug #17128 from Kevin Sweet
Discussion:
https://www.postgresql.org/message-id/flat/17128-55a8a879727a3e3a%40postgresql.or
Fix range check in ECPG numeric to int conversion
The previous coding guarded against -INT_MAX instead of INT_MIN,
leading to -2147483648 being rejected as out of range.
Per bug #17128 from Kevin Sweet
Discussion:
https://www.postgresql.org/message-id/flat/17128-55a8a879727a3e3a%40postgresql.or
