NNSqlValue has suspicious behavior around boundaries

[laysakura]

• negate() seems to fail in treat i64::MIN ( since |i64::MIN| == |i64::MAX| + 1 )
• Following test fails. ASTTranslator::integer_constant() should input positive number in string form ( - comes as UnaryOperator ). |i64::MIN| exceeds i64.

#[async_std::test]
async fn test_big_int() {
    SqlTest::default()
        .add_steps(Steps::BeginTransaction)
        .add_step(Step::new(
            "CREATE TABLE t (c BIGINT, PRIMARY KEY (c))",
            StepRes::Ok,
        ))
        .add_step(Step::new(
            format!("INSERT INTO t (c) VALUES ({})", i64::MIN),
            StepRes::Ok,
        ))
        .run()
        .await;
}

thread 'proptest_big_int' panicked at 'unexpected error ApllodbError {
    kind: NumericValueOutOfRange,
    desc: "integer value `9223372036854775808` could not be parsed as i64 (max supported size)",
    source: Some(
        ParseIntError {
            kind: PosOverflow,
        },
    ),
} on ApllodbServer::command() - step: Step {
    sql: "INSERT INTO t (c) VALUES (-9223372036854775808)",
    expected: StepRes::Ok,
}', apllodb-server/tests/sql_test/step.rs:81:26
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[laysakura]

なかなかエレガントな解法が思いつかないのでpend。

仕様として、 「SMALLINTは -i16::MAX ~ i16::MAX」 としてしまうのも手（一応SQL標準は確認したいが）。

[laysakura]

一応SQL標準は確認したいが

https://www.postgresql.jp/document/12/html/datatype-numeric.html
普通に i16::MIN ~ i16::MAX でした 🙄