Multiple DB queries about gonkey HOT 7 CLOSED

I also think that this functionality will be useful and improve tests readability.

Now we use the following workaround with cases:

  dbQuery: >
    {{ .query }}
  cases:
    - dbQueryArgs:
        query: SELECT 1
      dbResponse: 1
    - dbQueryArgs:
        query: SELECT 2
      dbResponse: 2

But that is verbose, non-intuitive and executes test again for each query.

from gonkey.

Why don't you use subqueries?

from gonkey.

SELECT
(
  SELECT id, name
  FROM items
),
(
  SELECT value
  FROM properties
)

would result in pq: subquery must return only one column as the first subquery selects two columns.

from gonkey.

Depends on data you trying to check. Usually i use COUNT funсtion in subqueries, to check that there are given number of records in some table. For ex:

(SELECT COUNT(*) AS value_count FROM properties WHERE value = 'my_value' AND item_id = id )

If you want to transpose rows to columns, check this out https://stackoverflow.com/questions/23060256/postgres-transpose-rows-to-columns

from gonkey.

Checking only count is quite a limiting functionality.

Thanks for pointing out crosstab function, it is indeed useful in some cases. But it adds a little bit of complication to both writing and reading tests. Besides it doesn't solve an issue of querying 2 and more independent tables. Using joins and crosstab() function may mislead readers about intentions of the author.

from gonkey.

I think we need change rule:
Test must contains request + response
to
Test must contains request + response OR dbQuery + dbResponse

from gonkey.

🚀 Issue was released in v1.18.0 🚀

from gonkey.