dutchmartin/sprattus

An async ORM for Postgres

sprattus's Issues

Connection pooling

We want to be able to use sprattus in a high performance web application. Therefore, connection pooling and maybe combining that with pipe-lining makes a lot of sense to do.

To come to an implementation, the following points are the concrete todo's:

• Look at the existing connection pooling solutions and find one that is async
• implement an async connection pool if it does not exits yet.
• Add support for sprattus and create benchmark results.

Add SSL/TLS support

Currently, we use the NoTls option of tokio-postgres. However, it would be nice to have SSL/TLS support as a option. To achieve that, a new constructor method that accepts the implementations that tokio-postgres already have available.

Name for the crate

Currently, the name of the project is 'profugus'. This name is intended to be temporary.
Therefore, we need a new name so we can release the crate with that name.

The current suggestions are:

• Sprat
• Loach
• Perch
• Pollock
• Anchovy
• Tetra
• Tuna
• Salmon

The observant reader probably noted that the suggested names all are fish that swim asynchronously from each other. And that is correct.

Namespace macro output

Instead of only writing Result<Self, Error>, write Result<Self, Sprattus::Error>
In this way, we overcome the problem of ambiguous naming, since other crates also have error types.

Remove the dependancy on strfmt

For some methods, we currently use the strfmt crate to generate sql query's. This seems unnecessary since the format macro can do this job too. Using the format macro will also reduce the amount of allocations needed which in result will improve performance.

Query builder

Currently, there is no way to fetch data from the database without writing SQL. Therefore we want to have a way to query more easily.
An idea for the api would be this:

let products = connection.select::<Product>().limit(10).orderAsc().await?

For complex query's, using SQL will be the preferred option, since a query builder can not provide all functions.

Create examples

Currently, the sprattus-test crate tests the library, but does not show how the library works with well documented examples. Therefore, having a examples directory would help users getting onboard