Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to reuse connection when using DSL?

See original GitHub issue

Each DSL operation calls self.client.execute which apparently creates a new connection each time. Passing a session to DSLSchema doesn’t work and causes an infinite recursion.

Traceback (most recent call last):
  File "gql_test2.py", line 45, in <module>
    query = ds.Query.listCasess().select(ds.ModelCasesConnection.items.select(ds.Cases.id))
  File "C:\Program Files\Python38\lib\site-packages\gql\dsl.py", line 38, in __getattr__
    type_def = self.schema.get_type(name)
  File "C:\Program Files\Python38\lib\site-packages\gql\dsl.py", line 38, in __getattr__
    type_def = self.schema.get_type(name)
  File "C:\Program Files\Python38\lib\site-packages\gql\dsl.py", line 38, in __getattr__
    type_def = self.schema.get_type(name)
  [Previous line repeated 996 more times]
RecursionError: maximum recursion depth exceeded

Is there some known good way to reuse the connection when using DSL? Is the session meant to work, and this is simply a bug?

Issue Analytics

State:
Created 3 years ago
Comments:5

Top GitHub Comments

1reaction

leszekhanuszcommented, Nov 21, 2020

Fixed in v3.0.0a5

0reactions

leszekhanuszcommented, Nov 14, 2020

I refactored the DSL code and the proposed way is a little bit different. Example:

query = dsl_gql(DSLQuery(ds.Query.hero.select(ds.Character.name)))                                                            
result = session.execute(query)