Skip to content

Advanced querying with Postgresql SQL

Besides Linq queries or simple raw SQL queries via session.Query<T>("where..."), it is also possible to do even more complex SQL queries via session.AdvancedSqlQueryAsync<T>(). With this method Marten does not try to add any missing parts to the SQL query, instead you have to provide the whole query string yourself.

Marten just makes some assumptions on how the schema of the SQl query result must look like, in order to be able to map the query result to documents, scalars or other JSON serializable types. With AdvancedSqlQueryAsync / AdvancedSqlQuery it is even possible to return multiple documents, objects and scalars as a tuple. Currently up to three result types can be queried for.

The following rules must be followed when doing queries with AdvancedSqlQueryAsync / AdvancedSqlQuery:

  • If a document should be returned, the SQL SELECT statement must contain all the columns required by Marten to build the document in the correct order. Which columns are needed depends on the session type and if any meta data are mapped to the document.
  • When having multiple return types, the columns required for each type must be enclosed in a SQL ROW statement.
  • For non-document types the column data must return the JSON that will be deserialized to this type.

For document types the correct order of columns in the result is:

  1. id - must always be present, except for QuerySession
  2. data - must always be present
  3. mt_doc_type - must be present only with document hierarchies
  4. mt_version - only when versioning is enabled
  5. mt_last_modified - only if this metadata is enabled
  6. mt_created_at - only if this metadata is enabled
  7. correlation_id - only if this metadata is enabled
  8. causation_id - only if this metadata is enabled
  9. last_modified_by - only if this metadata is enabled
  10. mt_deleted - only if this metadata is enabled
  11. mt_deleted_at - only if this metadata is enabled

You can always check the correct result column order, by inspecting the command text created from a Linq query: var commandText = session.Query<T>().ToCommand().CommandText;

Querying for a simple scalar value can be done like this:

var schema = session.DocumentStore.Options.Schema;
var name = (await session.AdvancedSqlQueryAsync<string>(
    $"select data ->> 'Name' from {schema.For<DocWithMeta>()} limit 1",

snippet source | anchor

Or for multiple scalars returned as a tuple:

var (number,text, boolean) = (await session.AdvancedSqlQueryAsync<int, string, bool>(
    "select row(5), row('foo'), row(true) from (values(1)) as dummy",

snippet source | anchor

You can also query for any arbitrary JSON that will get deserialized:

var result = (await session.AdvancedSqlQueryAsync<Foo, Bar>(
    "select row(json_build_object('Name', 'foo')), row(json_build_object('Name', 'bar')) from (values(1)) as dummy",

snippet source | anchor

Querying for documents requires to return the correct columns:

var schema = session.DocumentStore.Options.Schema;
var docs = await session.AdvancedSqlQueryAsync<DocWithoutMeta>(
    $"select id, data from {schema.For<DocWithoutMeta>()} order by data ->> 'Name'",

snippet source | anchor

If metadata are available, remember to add the correct metadata columns to the result. The order of the columns is important!:

var schema = session.DocumentStore.Options.Schema;
var doc = (await session.AdvancedSqlQueryAsync<DocWithMeta>(
    $"select id, data, mt_version from {schema.For<DocWithMeta>()} where data ->> 'Name' = 'Max'",

snippet source | anchor

You can also query for multiple related documents and scalar, e.g. for paging:

session.Store(new DocWithMeta { Id = 1, Name = "Max" });
session.Store(new DocDetailsWithMeta { Id = 1, Detail = "Likes bees" });
session.Store(new DocWithMeta { Id = 2, Name = "Michael" });
session.Store(new DocDetailsWithMeta { Id = 2, Detail = "Is a good chess player" });
session.Store(new DocWithMeta { Id = 3, Name = "Anne" });
session.Store(new DocDetailsWithMeta { Id = 3, Detail = "Hates soap operas" });
session.Store(new DocWithMeta { Id = 4, Name = "Beatrix" });
session.Store(new DocDetailsWithMeta { Id = 4, Detail = "Likes to cook" });
await session.SaveChangesAsync();

var schema = session.DocumentStore.Options.Schema;
IReadOnlyList<(DocWithMeta doc, DocDetailsWithMeta detail, long totalResults)> results =
    await session.AdvancedSqlQueryAsync<DocWithMeta, DocDetailsWithMeta, long>(
          row(,, a.mt_version),
          row(,, b.mt_version),
          row(count(*) over())
          {schema.For<DocWithMeta>()} a
        left join
          {schema.For<DocDetailsWithMeta>()} b on =
          ( ->> 'Id')::int > 1
        order by
 ->> 'Name'
        limit 2

results[0].detail.Detail.ShouldBe("Hates soap operas");
results[1].detail.Detail.ShouldBe("Likes to cook");

snippet source | anchor

For sync queries you can use the AdvancedSqlQuery<T>(...) overloads.

Getting document and schema names

Tables can be referenced with raw sql, but it is also possible to have marten tell you names of documents and aggregates.

These names can be found on the Schema property of the StoreOptions:

var schema = theSession.DocumentStore.Options.Schema;

snippet source | anchor

Using this you can resolve schemas:

var schema = theSession.DocumentStore.Options.Schema;


snippet source | anchor

And documents/aggregates:

var schema = theSession.DocumentStore.Options.Schema;


// `qualified: false` returns the table name without schema
schema.For<Account>(qualified: false).ShouldBe("mt_doc_account");
schema.For<Company>(qualified: false).ShouldBe("mt_doc_company");
schema.For<User>(qualified: false).ShouldBe("mt_doc_user");

snippet source | anchor

And also marten event tables:


schema.ForStreams(qualified: false).ShouldBe("mt_streams");
schema.ForEvents(qualified: false).ShouldBe("mt_events");
schema.ForEventProgression(qualified: false).ShouldBe("mt_event_progression");

snippet source | anchor

Released under the MIT License.