Explore >> Select a destination
|
You are here 
|
gatographql.com | ||
| | | | |
danganiev.me
|
|
| | | | | GraphQL might have started as a convenient way of delivering exactly the right amount of data from server to the client. But... | |
| | | | |
graphql-ruby.org
|
|
| | | | | [AI summary] This article explains the concept and benefits of persisted queries in GraphQL, including security, efficiency, and visibility improvements, along with implementation details using OperationStore. | |
| | | | |
brunoscheufler.com
|
|
| | | | | When you build a service focused around a GraphQL endpoint, you might think of testing strategies that can make use of it. After all, your resolvers will contain large parts of the actual business logic, otherwise, exposing an API wouldn't be useful, would it?... | |
| | | | |
jonathanlewis.wordpress.com
|
|
| | | I've discussed the capabilities of the dbms_xplan package in a couple of posts already; and shown how useful it can be in two examples: understanding a problem with filter subquery selectivity and understanding why some Cartesian merge joins were appearing unexpectedly. Let me make a crucial point about execution plans (again): if you have a... | ||
