Re:Why use GraphQL, good and bad reasons
by Someone on Saturday August 25, 2018 @01:24PM
(#17841646)
”But they should require just a few lines of configuration in GraphQL”
…assuming the presence of the equivalent of a complete enough SQL engine in the server, and often not even then, because adding a new stored procedure that can be called may mean extensive rethinking of the indexes you maintain, the way tables are partitioned, etc.
…assuming the presence of the equivalent of a complete enough SQL engine in the server, and often not even then, because adding a new stored procedure that can be called may mean extensive rethinking of the indexes you maintain, the way tables are partitioned, etc.