gem-hunter

This library provides the functionality required to access and manipulate data stored in a PostgreSQL database.

Add the PostgreSQL driver as a dependency to the Ballerina project.

Note: ballerinax/postgresql supports PostgrSQL driver versions above 42.2.18.

You can achieve this by importing the ballerinax/postgresql.driver module,

import ballerinax/postgresql.driver as _;

ballerinax/postgresql.driver package bundles the latest PostgreSQL driver JAR.

Tip: GraalVM native build is supported when ballerinax/postgresql is used along with the ballerinax/postgresql.driver

If you want to add a PostgreSQL driver of a specific version, you can add it as a dependency in Ballerina.toml. Follow one of the following ways to add the JAR in the file:

• Download the JAR and update the path

  [[platform.java21.dependency]]
  path = "PATH"
  

• Add JAR with a maven dependency params

  [[platform.java21.dependency]]
  groupId = "org.postgresql"
  artifactId = "postgresql"
  version = "42.6.1"
  

1. Enable Logical Replication:
   • Add the following lines to the PostgreSQL configuration file (postgresql.conf):

     wal_level = logical
     max_replication_slots = 4
     max_wal_senders = 4

   • Restart the PostgreSQL server to apply the changes:

     sudo service postgresql restart

To access a database, you must first create a postgresql:Client object. The examples for creating a PostgreSQL client can be found below.

Tip: The client should be used throughout the application lifetime.

This example shows the different methods of creating a postgresql:Client.

When the database is in the default username, the client can be created with an empty constructor, and thereby, the client will be initialized with the default properties.

postgresql:Client|sql:Error dbClient = new ();

The postgresql:Client receives the host, username, password, database, and port. Since the properties are passed in the same order as they are defined in the postgresql:Client, you can pass them without named parameters.

postgresql:Client|sql:Error dbClient2 = 
                                new ("localhost", "postgres", "postgres", 
                                     "postgres", 5432);

In the sample below, the postgresql:Client uses named parameters to pass the attributes since it is skipping some parameters in the constructor. Further, the postgresql:Options property is passed to configure the connection timeout in the PostgreSQL client.

postgresql:Options postgresqlOptions = {
  connectTimeout: 10
};
postgresql:Client|sql:Error dbClient = 
                                new (username = "postgres", password = "postgres", 
                                     database = "test", options = postgresqlOptions);

Similarly in the sample below, the postgresql:Client uses named parameters and it provides an unshared connection pool of the type of sql:ConnectionPool to be used within the client. For more details about connection pooling, see the sql library.

postgresql:Client|sql:Error dbClient4 = 
                                new (username = "postgres", password = "postgres",
                                     connectionPool = {maxOpenConnections: 5});

To connect to the PostgreSQL server using an SSL connection, you must add the SSL configurations to the postgresql:Options when creating the postgresql:Client. For the SSL Mode, you can select one of the following modes: postgresql:PREFERRED, postgresql:REQUIRED, postgresql:DISABLE, or postgresql:ALLOW, postgresql:VERIFY_CA, or postgresql:VERIFY_IDENTITY according to the requirement. The key files must be provided in the .p12 format.

string clientStorePath = "/path/to/keystore.p12";

postgresql:Options postgresqlOptions = {
    ssl: {
        mode: postgresql:ALLOW,
        key: {
            path: clientStorePath,
            password: "ballerina"
        }
    }
};

All database libraries share the same connection pooling concept and there are three possible scenarios for connection pool handling. For its properties and possible values, see the sql:ConnectionPool.

Note: Connection pooling is used to optimize opening and closing connections to the database. However, the pool comes with an overhead. It is best to configure the connection pool properties as per the application need to get the best performance.

1. Global, shareable, default connection pool

   If you do not provide the connectionPool field when creating the database client, a globally-shareable pool will be created for your database unless a connection pool matching with the properties you provided already exists.

   postgresql:Client|sql:Error dbClient = 
                                   new (username = "postgres", password = "postgres", 
                                        database = "test");

2. Client-owned, unsharable connection pool

   If you define the connectionPool field inline when creating the client with the sql:ConnectionPool type, an unsharable connection pool will be created.

   postgresql:Client|sql:Error dbClient = 
                                   new (username = "postgres", password = "postgres", 
                                        database = "test", 
                                        connectionPool = { maxOpenConnections: 5 });

3. Local, shareable connection pool

   If you create a record of the sql:ConnectionPool type and reuse that in the configuration of multiple clients, for each set of clients that connects to the same database instance with the same set of properties, a shared connection pool will be used.

   sql:ConnectionPool connPool = {maxOpenConnections: 5};
   
   postgresql:Client|sql:Error dbClient1 =
                                   new (username = "postgres", password = "postgres", 
                                   database = "test", connectionPool = connPool);
   postgresql:Client|sql:Error dbClient2 = 
                                   new (username = "postgres", password = "postgres", 
                                   database = "test", connectionPool = connPool);
   postgresql:Client|sql:Error dbClient3 = 
                                   new (username = "postgres", password = "postgres",
                                   database = "example", connectionPool = connPool);

For more details about each property, see the postgresql:Client.

The postgresql:Client references sql:Client and all the operations defined by the sql:Client will be supported by the postgresql:Client as well.

Once all the database operations are performed, you can close the client you have created by invoking the close() operation. This will close the corresponding connection pool if it is not shared by any other database clients.

Note: The client must be closed only at the end of the application lifetime (or closed for graceful stops in a service).

error? e = dbClient.close();

or

check dbClient.close();

Once the client is created, database operations can be executed through that client. This library defines the interface and common properties that are shared among multiple database clients. It also supports querying, inserting, deleting, updating, and batch updating data.

The sql:ParameterizedQuery is used to construct the SQL query to be executed by the client. You can create a query with constant or dynamic input data as follows.

Query with constant values

sql:ParameterizedQuery query = `SELECT * FROM students 
                                WHERE id < 10 AND age > 12`;

Query with dynamic values

int[] ids = [10, 50];
int age = 12;
sql:ParameterizedQuery query = `SELECT * FROM students 
                                WHERE id < ${ids[0]} AND age > ${age}`;

Moreover, the SQL package has sql:queryConcat() and sql:arrayFlattenQuery() util functions which make it easier to create a dynamic/constant complex query.

The sql:queryConcat() is used to create a single parameterized query by concatenating a set of parameterized queries. The sample below shows how to concatenate queries.

int id = 10;
int age = 12;
sql:ParameterizedQuery query = `SELECT * FROM students`;
sql:ParameterizedQuery query1 = ` WHERE id < ${id} AND age > ${age}`;
sql:ParameterizedQuery sqlQuery = sql:queryConcat(query, query1);

A query with the IN operator can be created using the sql:ParameterizedQuery as shown below. Here you need to flatten the array and pass each element separated by a comma.

int[] ids = [1, 2, 3];
sql:ParameterizedQuery query = `SELECT count(*) as total FROM DataTable 
                                WHERE row_id IN (${ids[0]}, ${ids[1]}, ${ids[2]})`;

The sql:arrayFlattenQuery() util function is used to make the array flattening easier. It makes the inclusion of varying array elements into the query easier by flattening the array to return a parameterized query. You can construct the complex dynamic query with the IN operator by using both functions as shown below.

int[] ids = [1, 2];
sql:ParameterizedQuery sqlQuery = 
                         sql:queryConcat(`SELECT * FROM DataTable WHERE id IN (`, 
                                          sql:arrayFlattenQuery(ids), `)`);

This sample creates a table with three columns. The first column is a primary key of type int while the second column is of type int and the other is of type varchar. The CREATE statement is executed via the execute remote method of the client.

// Create the ‘Students’ table with the ‘id’, ’name’, and ’age’ fields.
sql:ExecutionResult result = 
                check dbClient->execute(`CREATE TABLE student (
                                           id INT SERIAL,
                                           age INT, 
                                           name VARCHAR(255), 
                                           PRIMARY KEY (id)
                                         )`);
// A value of the `sql:ExecutionResult` type is returned for the `result`. 

These samples show the data insertion by executing an INSERT statement using the execute remote method of the client.

In this sample, the query parameter values are passed directly into the query statement of the execute remote method.

sql:ExecutionResult result = check dbClient->execute(`INSERT INTO student(age, name)
                                                        VALUES (23, 'john')`);

In this sample, the parameter values, which are assigned to local variables are used to parameterize the SQL query in the execute remote method. This type of parameterized SQL query can be used with any primitive Ballerina type such as string, int, float, or boolean and in that case, the corresponding SQL type of the parameter is derived from the type of the Ballerina variable that is passed.

string name = "Anne";
int age = 8;

sql:ParameterizedQuery query = `INSERT INTO student(age, name)
                                  VALUES (${age}, ${name})`;
sql:ExecutionResult result = check dbClient->execute(query);

In this sample, the parameter values are passed as an sql:TypedValue to the execute remote method. Use the corresponding subtype of the sql:TypedValue such as sql:VarcharValue, sql:CharValue, sql:IntegerValue, etc., when you need to provide more details such as the exact SQL type of the parameter.

sql:VarcharValue name = new ("James");
sql:IntegerValue age = new (10);

sql:ParameterizedQuery query = `INSERT INTO student(age, name)
                                  VALUES (${age}, ${name})`;
sql:ExecutionResult result = check dbClient->execute(query);

This sample demonstrates inserting data while returning the auto-generated keys. It achieves this by using the execute remote method to execute the INSERT statement.

int age = 31;
string name = "Kate";

sql:ParameterizedQuery query = `INSERT INTO student(age, name)
                                  VALUES (${age}, ${name})`;
sql:ExecutionResult result = check dbClient->execute(query);

//Number of rows affected by the execution of the query.
int? count = result.affectedRowCount;

//The integer or string generated by the database in response to a query execution.
string|int? generatedKey = result.lastInsertId;

These samples show how to demonstrate the different usages of the query operation to query the database table and obtain the results as a stream.

Note: When processing the stream, make sure to consume all fetched data or close the stream.

This sample demonstrates querying data from a table in a database. First, a type is created to represent the returned result set. This record can be defined as an open or a closed record according to the requirement. If an open record is defined, the returned stream type will include both defined fields in the record and additional database columns fetched by the SQL query which are not defined in the record. Note the mapping of the database column to the returned record's property is case-insensitive if it is defined in the record (i.e., the ID column in the result can be mapped to the id property in the record). Additional column names are added to the returned record as in the SQL query. If the record is defined as a closed record, only the fields defined in the record are returned or gives an error when additional columns are present in the SQL query. Next, the SELECT query is executed via the query remote method of the client. Once the query is executed, each data record can be retrieved by iterating through the result set. The stream returned by the SELECT operation holds a pointer to the actual data in the database, and it loads data from the table only when it is accessed. This stream can be iterated only once.

// Define an open record type to represent the results.
type Student record {
    int id;
    int age;
    string name;
};

// Select the data from the database table. The query parameters are passed 
// directly. Similar to the `execute` samples, parameters can be passed as
// sub types of `sql:TypedValue` as well.
int id = 10;
int age = 12;
sql:ParameterizedQuery query = `SELECT * FROM students
                                WHERE id < ${id} AND age > ${age}`;
stream<Student, sql:Error?> resultStream = dbClient->query(query);

// Iterating the returned table.
check from Student student in resultStream
    do {
       // Can perform operations using the `student` record of type `Student`.
    };

Defining the return type is optional and you can query the database without providing the result type. Hence, the above sample can be modified as follows with an open record type as the return type. The property name in the open record type will be the same as how the column is defined in the database.

// Select the data from the database table. The query parameters are passed 
// directly. Similar to the `execute` samples, parameters can be passed as 
// sub types of `sql:TypedValue` as well.
int id = 10;
int age = 12;
sql:ParameterizedQuery query = `SELECT * FROM students
                                WHERE id < ${id} AND age > ${age}`;
stream<record{}, sql:Error?> resultStream = dbClient->query(query);

// Iterating the returned table.
check from record{} student in resultStream
    do {
        // Can perform operations using the `student` record.
        io:println("Student name: ", student.value["name"]);
    };

There are situations in which you may not want to iterate through the database and in that case, you may decide to use the queryRow() operation. If the provided return type is a record, this method returns only the first row retrieved by the query as a record.

int id = 10;
sql:ParameterizedQuery query = `SELECT * FROM students WHERE id = ${id}`;
Student retrievedStudent = check dbClient->queryRow(query);

The queryRow() operation can also be used to retrieve a single value from the database (e.g., when querying using COUNT() and other SQL aggregation functions). If the provided return type is not a record (i.e., a primitive data type) , this operation will return the value of the first column of the first row retrieved by the query.

int age = 12;
sql:ParameterizedQuery query = `SELECT COUNT(*) FROM students WHERE age < ${age}`;
int youngStudents = check dbClient->queryRow(query);

This sample demonstrates modifying data by executing an UPDATE statement via the execute remote method of the client.

int age = 23;
sql:ParameterizedQuery query = `UPDATE students SET name = 'John' WHERE age = ${age}`;
sql:ExecutionResult result = check dbClient->execute(query);

This sample demonstrates deleting data by executing a DELETE statement via the execute remote method of the client.

string name = "John";
sql:ParameterizedQuery query = `DELETE from students WHERE name = ${name}`;
sql:ExecutionResult result = check dbClient->execute(query);

This sample demonstrates how to insert multiple records with a single INSERT statement that is executed via the batchExecute remote method of the client. This is done by creating a table with multiple records and parameterized SQL query as same as the above execute operations.

// Create the table with the records that need to be inserted.
var data = [
  { name: "John", age: 25 },
  { name: "Peter", age: 24 },
  { name: "jane", age: 22 }
];

// Do the batch update by passing the batches.
sql:ParameterizedQuery[] batch = from var row in data
                                 select `INSERT INTO students ('name', 'age')
                                           VALUES (${row.name}, ${row.age})`;
sql:ExecutionResult[] result = check dbClient->batchExecute(batch);

This sample demonstrates how to execute a stored procedure with a single INSERT statement that is executed via the call remote method of the client.

int uid = 10;
sql:IntegerOutParameter insertId = new;

sql:ProcedureCallResult result = 
                         check dbClient->call(`call InsertPerson(${uid}, ${insertId})`);
stream<record{}, sql:Error?>? resultStr = result.queryResult;
if resultStr is stream<record{}, sql:Error?> {
    check from record{} result in resultStr
        do {
            // Can perform operations using the `result` record.
        };
}
check result.close();

Note: Once the results are processed, the close method on the sql:ProcedureCallResult must be called.

Note: The default thread pool size used in Ballerina is: the number of processors available * 2. You can configure the thread pool size by using the BALLERINA_MAX_POOL_SIZE environment variable.

To listen for change data capture (CDC) events from a Postgres database, you must create a postgresql:CdcListener object. The listener allows your Ballerina application to react to changes (such as inserts, updates, and deletes) in real time.

You can create a CDC listener by specifying the required configurations such as host, port, username, password, and database name. Additional options can be provided using the cdc:Options record.

listener postgresql:CdcListener cdcListener = new (database = {
    username: <username>,
    password: <password>
});

You can attach a service to the listener to handle CDC events. The service can define remote methods for different event types such as onRead, onCreate, onUpdate, and onDelete.

service on cdcListener {
    remote function onRead(record{} after) returns cdc:Error? {
        io:println("Insert event: ", after);
    }

    remote function onCreate(record{} after) returns cdc:Error? {
        io:println("Insert event: ", after);
    }

    remote function onUpdate(record{} before, record{} after) returns cdc:Error? {
        io:println("Update event - Before: ", before, " After: ", after);
    }

    remote function onDelete(record{} before) returns error? {
        io:println("Delete event: ", before);
    }
}

Issues and Projects tabs are disabled for this repository as this is part of the Ballerina Standard Library. To report bugs, request new features, start new discussions, view project boards, etc, visit the Ballerina Standard Library parent repository.

This repository only contains the source code for the package.

1. Download and install Java SE Development Kit (JDK) version 11 (from one of the following locations).

   • Oracle
   • OpenJDK

2. Download and install Docker.

3. Export your Github Personal access token with the read package permissions as follows.

    export packageUser=<Username>
    export packagePAT=<Personal access token>
   

Execute the commands below to build from the source.

1. To build the library:

    ./gradlew clean build
   

2. To run the integration tests:

    ./gradlew clean test
   

3. To build the package without tests:

    ./gradlew clean build -x test
   

4. To run only specific tests:

    ./gradlew clean build -Pgroups=<Comma separated groups/test cases>
   

   Tip: The following groups of test cases are available.

   Groups	Test Cases
   connection	connection-init
   pool	pool
   execute	execute-basic execute-params
   batch-execute	batch-execute
   query	query query-simple-params
   procedures	procedures
   functions	functions

5. To disable some specific groups during the test:

    ./gradlew clean build -Pdisable-groups=<Comma separated groups/test cases>
   

6. To debug the tests:

    ./gradlew clean build -Pdebug=<port>
   

7. To debug the package with the Ballerina language:

    ./gradlew clean build -PbalJavaDebug=<port>   
   

8. Publish ZIP artifact to the local .m2 repository:

   ./gradlew clean build publishToMavenLocal
   

9. Publish the generated artifacts to the local Ballerina central repository:

   ./gradlew clean build -PpublishToLocalCentral=true
   

As an open source project, Ballerina welcomes contributions from the community.

For more information, go to the contribution guidelines.

All contributors are encouraged to read the Ballerina Code of Conduct.

• For more information go to the postgresql library.
• For example demonstrations of the usage, go to Ballerina By Examples.
• Chat live with us via our Discord server.
• Post all technical questions on Stack Overflow with the #ballerina tag.