graphql-engine/server/tests-py/queries/graphql_mutation/insert
Auke Booij b2ad3ee2ee
server: avoid integer overflows (fix #576) (fix #4368) (#4435)
* Update graphql-parser-hs and hence use `Scientific` directly

The new version of graphql-parser-hs returns Scientific and Integer
rather than Double and Int32, respectively.  So we now need to do less
work in graphql-engine, and we can process larger numbers.

In practice, this means that when inserting a bigint, we no longer
need to specify the inserted integer as text.  This is also
represented in the updated tests.

* Generate int overflow error on insert

* Document bigint insertion support in changelog
2020-04-21 15:56:15 +02:00
..
basic server: avoid integer overflows (fix #576) (fix #4368) (#4435) 2020-04-21 15:56:15 +02:00
constraints introduce v1/graphql (fix #1368) (#2064) 2019-05-10 11:35:10 +05:30
geojson Test with postgis 3.0.0 (#3519) 2019-12-18 19:32:15 -06:00
nested allow custom mutations through actions (#3042) 2020-02-13 23:08:23 +05:30
nullprefixcolumn Allow field names to start with reserved keywords (fix #3597) (#3927) 2020-04-02 00:27:43 -05:00
onconflict Fix result ordering in some incorrect tests 2019-11-05 15:15:25 -06:00
permissions fix postgres query error when computed fields included in mutation response, fix #4035 2020-03-11 10:23:28 +05:30
views fix few bugs related to nested insert returning (fix #3609, #3642, #3271) (#3618) 2020-02-04 21:04:17 +05:30