Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.oxla.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Dapper is a simple object-relational mapper (ORM) for .NET. It provides an easy and efficient way to query databases with minimal setup and overhead, leveraging SQL directly while mapping results to C# objects. This page describes how to use Dapper with Npgsql (a PostgreSQL data provider for .NET) to connect to Oxla.

​
Establishing connection

There are two ways that can be utilised in order to establish a connection through Npgsql:
  • Npgsql’s DataSource Class
var connectionString = "Server=127.0.0.1:5432;Username=user;Password=password;Database=db;";
var dataSource = NpgsqlDataSource.Create(connectionString);
var connection = dataSource.OpenConnection();
  • Creating Connection Directly
var connectionString = "Server=127.0.0.1:5432;Username=user;Password=password;Database=db;";
var connection = new NpgsqlConnection(connectionString);
connection.Open();
For more details on connection string options, including SSL configuration, please refer to Npgsql docs.

​
Example Usage

This example shows basic query execution for the following C# class, once the connection has been established: 
public class Customer
{
    public int ClientId { get; set; }
    public double Height { get; set; }
    public string FirstName { get; set; }
}

connection.Execute("CREATE TABLE Customer (ClientId INTEGER, Height DOUBLE, FirstName TEXT)");

var customer = new Customer{ClientId = 1, Height = 3.14, FirstName = "John"};
connection.Execute("INSERT INTO Customer VALUES (@ClientId, @Height, @FirstName)", customer);

var customers = connection.Query<Customer>("SELECT * FROM Customer");
foreach(var c in customers)
{
    Console.WriteLine($"Customer #{c.ClientId}: {c.FirstName} is {c.Height} tall.");
}
INSERT INTO Customer VALUES (@ClientId, @Height, @FirstName) syntax uses prepared statements under the hood, which are not supported by Oxla. We translate incoming binary input back into string, thus no benefits of such statements apply (no security or performance improvements)

​
Unsupported Functions & Structures

Here you can find a list of functions and potentially related structures, that we either do not support at all or they work incorrectly when combining Oxla and Dapper-Npgsql: