File: edgedb.rst

package info (click to toggle)
python-msgspec 0.19.0-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 6,356 kB
  • sloc: javascript: 23,944; ansic: 20,540; python: 20,465; makefile: 29; sh: 19
file content (224 lines) | stat: -rw-r--r-- 6,759 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
Usage with EdgeDB
=================

.. image:: ../_static/edgedb.svg
   :width: 60%
   :align: center

`EdgeDB <https://www.edgedb.com/>`__ is an interesting new `graph-relational
database <https://www.edgedb.com/blog/the-graph-relational-database-defined>`__
system. It includes a powerful and ergonomic query language `"EdgeQL"
<https://www.edgedb.com/docs/edgeql/index>`__, along with client libraries that
integrate well with their respective language ecosystems.

In this example we demonstrate a few ways of integrating EdgeDB's
`Python client library <https://www.edgedb.com/docs/clients/python>`__
with ``msgspec``.

Setup
-----

This is not intended to be a complete EdgeDB tutorial; for that we recommend
going through the `official EdgeDB quickstart
<https://www.edgedb.com/docs/intro/quickstart>`__. This example assumes you
already have the EdgeDB CLI and Python library installed.

After cloning the ``msgspec`` repo, navigate to the ``edgedb`` example
directory `here
<https://github.com/jcrist/msgspec/blob/main/examples/edgedb>`__. Then
initialize a new ``edgedb`` project.

.. code-block:: bash

    $ edgedb project init --server-instance edgedb-msgspec-example --non-interactive


This will setup a new instance and apply the example schema:

.. literalinclude:: ../../../examples/edgedb/dbschema/default.esdl

We then need to insert some records. This is done with the following EdgeQL
query:

.. literalinclude:: ../../../examples/edgedb/insert_data.edgeql

To run this, execute the following:

.. code-block:: bash

    $ edgedb query -f insert_data.edgeql


JSON Encoding Query Results
---------------------------

The EdgeDB Python library returns objects as ``edgedb.Object`` instances
(`docs <https://www.edgedb.com/docs/clients/python/api/types#edgedb.Object>`__).
Here we query the movie "Dune" that we inserted above, requesting the movie
title and actors' names.

.. code-block:: python

    >>> import edgedb

    >>> import msgspec

    >>> client = edgedb.create_client()

    >>> dune = client.query_single(
    ...     """
    ...     SELECT Movie {
    ...         title,
    ...         actors: {
    ...             name
    ...         }
    ...     }
    ...     FILTER .title = 'Dune'
    ...     LIMIT 1
    ...     """
    ... )

    >>> dune
    Object{title := 'Dune', actors := [Object{name := 'Timothée Chalamet'}, Object{name := 'Zendaya'}]}

    >>> type(dune)
    edgedb.Object


These ``edgedb.Object`` instances are duck-type compatible with `dataclasses`,
which means ``msgspec`` already knows how to JSON encode them.

.. code-block:: python

    >>> json = msgspec.json.encode(dune)

    >>> print(msgspec.json.format(json.decode()))  # pretty-print the JSON
    {
      "id": "b21913c4-3b68-11ee-89b0-2f0b6819503d",
      "title": "Dune",
      "actors": [
        {
          "id": "b219195a-3b68-11ee-89b0-5b3794805cc7",
          "name": "Timothée Chalamet"
        },
        {
          "id": "b2192058-3b68-11ee-89b0-f7d83b95fb13",
          "name": "Zendaya"
        }
      ]
    }

Note that if you're immediately JSON encoding the results you may be better
served by using EdgeDB's ``query_json``/``query_single_json`` methods, which
return JSON strings directly (but strip the ``id`` fields).

.. code-block:: python

    >>> edgedb_json = client.query_single_json(
    ...     """
    ...     SELECT Movie {
    ...         title,
    ...         actors: {
    ...             name
    ...         }
    ...     }
    ...     FILTER .title = 'Dune'
    ...     LIMIT 1
    ...     """
    ... )

    >>> edgedb_json
    '{"title" : "Dune", "actors" : [{"name" : "Timothée Chalamet"},{"name" : "Zendaya"}]}'

If needed, this JSON string may be efficiently composed into a larger JSON
object using `msgspec.Raw`. Here we add some additional outer structure
wrapping the query result:

.. code-block:: python

    >>> import datetime

    >>> msg = {
    ...     "timestamp": datetime.datetime.now(datetime.timezone.utc),
    ...     "server_version": "3.2",
    ...     "query_result": msgspec.Raw(edgedb_json),
    ... }

    >>> json = msgspec.json.encode(msg)

    >>> print(msgspec.json.format(json.decode()))  # pretty-print the JSON
    {
      "timestamp": "2023-08-15T14:37:12.733731Z",
      "server_version": "3.2",
      "query_result": {
        "title": "Dune",
        "actors": [
          {
            "name": "Timothée Chalamet"
          },
          {
            "name": "Zendaya"
          }
        ]
      }
    }

Supporting Other EdgeDB Types
-----------------------------

Besides ``edgedb.Object``, ``msgspec`` also includes builtin support for JSON
encoding ``edgedb.NamedTuple`` types. There are a few remaining ``edgedb``
types that ``msgspec`` doesn't support out-of-the-box:

- ``edgedb.DateDuration`` (`docs <https://www.edgedb.com/docs/clients/python/api/types#edgedb.DateDuration>`__)
- ``edgedb.RelativeDuration`` (`docs <https://www.edgedb.com/docs/clients/python/api/types#edgedb.RelativeDuration>`__)

JSON encoding support for these may be added through the use of
:doc:`extensions <../extending>`.

.. code-block:: python

    >>> def enc_hook(obj):
    ...     if isinstance(obj, (edgedb.DateDuration, edgedb.RelativeDuration)):
    ...         # The str representation of these types are ISO8601 durations,
    ...         return str(obj)
    ...     # Raise a NotImplementedError for unsupported types
    ...     raise NotImplementedError

    >>> duration = client.query_single('SELECT <cal::date_duration>"1 year 2 days"')

    >>> duration
    <edgedb.DateDuration "P1Y2D">

    >>> msgspec.json.encode(duration, enc_hook=enc_hook)
    b'"P1Y2D"'

Converting Results to Structs
-----------------------------

If your application contains complex server-side logic, you may wish to convert
the query results into some other application-specific structured type.
``msgspec`` supports automatic conversion to other types `msgspec.convert`.

Here we'll define two `msgspec.Struct` types mirroring our Schema above:

.. code-block:: python

    >>> class Person(msgspec.Struct):
    ...     name: str

    >>> class Movie(msgspec.Struct):
    ...     title: str
    ...     actors: list[Person]

We can then convert the ``edgedb.Object`` results into our ``Struct`` types
using `msgspec.convert`. Note that the same conversion process would work if
``Person`` or ``Movie`` were defined as `dataclasses` or `attrs` types instead.

.. code-block:: python

    >>> msgspec.convert(dune, Movie, from_attributes=True)
    Movie(title='Dune', actors=[Person(name='Timothée Chalamet'), Person(name='Zendaya')])

These structs may then be used to implement application logic
(mutating/combining them as needed) before serializing the output to JSON.