Default package

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message Backtrace

rethinkdb_spec.proto:107

Used in: Response

message Datum

rethinkdb_spec.proto:193

A [Datum] is a chunk of data that can be serialized to disk or returned to the user in a Response. Currently we only support JSON types, but we may support other types in the future (e.g., a date type or an integer type).

Used in: Datum.AssocPair, Response, Term

message Datum.AssocPair

rethinkdb_spec.proto:212

Used in: Datum

enum Datum.DatumType

rethinkdb_spec.proto:194

Used in: Datum

message Frame

rethinkdb_spec.proto:98

A backtrace frame (see `backtrace` in Response below)

Used in: Backtrace

enum Frame.FrameType

rethinkdb_spec.proto:99

Used in: Frame

message Query

rethinkdb_spec.proto:67

You send one of: * A [START] query with a [Term] to evaluate and a unique-per-connection token. * A [CONTINUE] query with the same token as a [START] query that returned [SUCCESS_PARTIAL] in its [Response]. * A [STOP] query with the same token as a [START] query that you want to stop. * A [NOREPLY_WAIT] query with a unique per-connection token. The server answers with a [WAIT_COMPLETE] [Response].

message Query.AssocPair

rethinkdb_spec.proto:90

Used in: Query

enum Query.QueryType

rethinkdb_spec.proto:68

Used in: Query

message Response

rethinkdb_spec.proto:112

You get back a response with the same [token] as your query.

enum Response.ResponseNote

rethinkdb_spec.proto:142

ResponseNotes are used to provide information about the query response that may be useful for people writing drivers or ORMs. Currently all the notes we send indicate that a stream has certain special properties.

Used in: Response

enum Response.ResponseType

rethinkdb_spec.proto:113

Used in: Response

message Term

rethinkdb_spec.proto:264

A [Term] is either a piece of data (see **Datum** above), or an operator and its operands. If you have a [Datum], it's stored in the member [datum]. If you have an operator, its positional arguments are stored in [args] and its optional arguments are stored in [optargs]. A note about type signatures: We use the following notation to denote types: arg1_type, arg2_type, argrest_type... -> result_type So, for example, if we have a function `avg` that takes any number of arguments and averages them, we might write: NUMBER... -> NUMBER Or if we had a function that took one number modulo another: NUMBER, NUMBER -> NUMBER Or a function that takes a table and a primary key of any Datum type, then retrieves the entry with that primary key: Table, DATUM -> OBJECT Some arguments must be provided as literal values (and not the results of sub terms). These are marked with a `!`. Optional arguments are specified within curly braces as argname `:` value type (e.x `{use_outdated:BOOL}`) Many RQL operations are polymorphic. For these, alterantive type signatures are separated by `|`. The RQL type hierarchy is as follows: Top DATUM NULL BOOL NUMBER STRING OBJECT SingleSelection ARRAY Sequence ARRAY Stream StreamSelection Table Database Function Ordering - used only by ORDER_BY Pathspec -- an object, string, or array that specifies a path Error

Used in: Query, Query.AssocPair, Term.AssocPair

message Term.AssocPair

rethinkdb_spec.proto:755

Used in: Term

enum Term.TermType

rethinkdb_spec.proto:265

Used in: Term

message VersionDummy

rethinkdb_spec.proto:42

We need to wrap it like this for some

(message has no fields)

enum VersionDummy.Protocol

rethinkdb_spec.proto:54

The protocol to use after the handshake, specified in V0_3

enum VersionDummy.Version

rethinkdb_spec.proto:46

non-conforming protobuf libraries This enum contains the magic numbers for your version. See **THE HIGH-LEVEL VIEW** for what to do with it.