@@ -741,7 +741,7 @@ changes:
741741 be retained for a long time and likely reused many times. SQLite currently
742742 responds to this hint by avoiding lookaside memory. Corresponds to the
743743 [ ` SQLITE_PREPARE_PERSISTENT ` ] [ ] flag. ** Default:** ` false ` .
744- * Returns: {StatementSync } The prepared statement.
744+ * Returns: {Statement } The prepared statement.
745745
746746Compiles a SQL statement into a [ prepared statement] [ ] . This method is a wrapper
747747around [ ` sqlite3_prepare_v3() ` ] [ ] .
@@ -1151,7 +1151,7 @@ Closes the session. If the session is already closed, then this is a no-op. An
11511151a changeset or patchset, or if the method is called from a callback that SQLite
11521152invoked, under the same conditions as [` session .close ()` ][].
11531153
1154- ## Class: ` StatementSync `
1154+ ## Class: ` Statement `
11551155
11561156<!-- YAML
11571157added: v22.5.0
@@ -1162,6 +1162,10 @@ instantiated via its constructor. Instead, instances are created via the
11621162` database .prepare ()` method. All APIs exposed by this class execute
11631163synchronously.
11641164
1165+ ` StatementSync` is a deprecated alias for ` Statement` , kept for backward
1166+ compatibility with the class's previous name. See
1167+ [DEP0211](deprecations.md#dep0211-sqlitestatementsync).
1168+
11651169A prepared statement is an efficient binary representation of the SQL used to
11661170create it. Prepared statements are parameterizable, and can be invoked multiple
11671171times with different bound values. Parameters also offer protection against
0 commit comments