Surrealist

Latest version: v1.1.1

Safety actively analyzes 714736 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 5

1.0.1

add run method for connections and run_function for Database (https://surrealdb.com/docs/surrealdb/integration/rpc#run)
add insert_relation method for connections (https://surrealdb.com/docs/surrealdb/integration/rpc#insert_relation)
add version method for connections (https://surrealdb.com/docs/surrealdb/integration/rpc#version)
add info method for connections (https://surrealdb.com/docs/surrealdb/integration/rpc#info)
add relate method for connections (https://surrealdb.com/docs/surrealdb/integration/rpc#relate)
add graphql method for connections (https://surrealdb.com/docs/surrealdb/integration/rpc#graphql)
minor fixes for docs and examples

1.0.0

- both http and ws connections lost signin, signup, authenticate, invalidate methods, sign in now happen under the hood on connecting
- USE method for http just adds headers "surreal-db" and "surreal-ns" for http-requests
- websocket client under the hood uses explicit "sec-websocket-protocol"="json" header
- http now uses rpc-protocol instead of different endpoints and methods
- for root user now you should connect only with credentials and then call use method (see [examples](https://github.com/kotolex/surrealist/tree/master/examples/connect.py))
- you can now specify access method on connecting via a Surreal/Database object
- now use Bearer instead of Basic for Authorization
- database argument is now optional for USE method, but raises for websocket if a database is not specified
- all QL-statements now have SurrealQL Syntax in documentation for class
- all DEFINE statements now have COMMENT finished statement
- now DEFINE TOKEN use Algorithm enum
- Database object can be created from active connection with `Database.from_connection(connection)`
- Connection can be extracted from Database with `Database.get_connection()`
- improve DEFINE ANALYZER, now it uses predefined methods for tokenizers and filters, and has documentation for all of them
- SELECT statement can use TEMPFILES clause on all levels except EXPLAIN (which is the last one)
- update DEFINE USER statement
- add UPSERT statement
- add DEFINE ACCESS JWT and DEFINE ACCESS RECORD statements
- add REMOVE ACCESS statement
- add ALTER TABLE statement
- add ENFORCED statement for DEFINE TABLE
- add CONCURRENTLY statement for DEFINE INDEX
- deprecate DEFINE TOKEN-REMOVE TOKEN and DEFINE SCOPE-REMOVE SCOPE
- let and unset now raises CompatibilityError for http
- add upsert method to Connection
- all DEFINE statements except SCOPE/TOKEN now have OVERWRITE clause
- Connection objects now store token after authorize
- more examples and tests, fix old examples
- fix Readme, add compatibility table

0.5.3

minor fixes for docs and examples

0.5.2

- now user should use standard logging for debug
- remove log_level arguments for classes
- add LOG_FORMAT for default uses
- fix README

0.5.1

- add more precise names for INDEX methods (M, TYPE)
- limit allowed options for some methods (TYPE)
- add documentation for index methods
- change BM25 (add docs and parameters)
- fix validate method bug for changefeed
- fix README, examples and tests

0.5.0

- although INCLUDE ORIGINAL statement exists, it has no effect (SurrealDB team decision for 1.5.0)
- add REBUILD INDEX statement, usable for database and table objects
- improve DEFINE INDEX statement, now it can use MTREE and HNSW indexes
- fix https://github.com/kotolex/surrealist/issues/44 , so now set() and other methods which has optional string and
keyword-arguments for QL will combine string and kwargs
- add INFO ... STRUCTURE feature as optional, by default it is not used as it is for internal use of SDB
- add more examples and tests

Page 3 of 5

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.