### Establish Firebird Connection

Source: https://github.com/fernandobatels/rsfbclient/blob/master/rsfbclient-diesel/README.md

Use `FbConnection::establish` to connect to a Firebird database. Ensure you have the necessary connection string format.

```rust
use diesel::prelude::*;
use rsfbclient_diesel::FbConnection;

let conn = FbConnection::establish("firebird://SYSDBA:masterkey@localhost/test.fdb");

```

--------------------------------

### Run Tests Locally

Source: https://github.com/fernandobatels/rsfbclient/blob/master/CONTRIBUTING.md

Command to run all tests in a single thread to ensure consistency, mirroring the GitHub Actions workflow. Avoid running `cargo test` without the `-- --test-threads 1` flag to prevent potential test failures due to concurrent database transactions.

```bash
cargo test -- --test-threads 1
```

--------------------------------

### Commit Message Template

Source: https://github.com/fernandobatels/rsfbclient/blob/master/CONTRIBUTING.md

A recommended structure for commit messages, separating a concise header from a detailed body. This format aids readability in various Git tools.

```git
Header line: explain the commit in one line

Body of commit message is a few lines of text, explaining things in more
detail, possibly giving some background about the issue being fixed, etc
etc.

It is important that the header be one line that is not too long This is
because many tools (including github) will show only this line in some
parts of their UI

The body of the commit message can be several paragraphs.  Please do
proper word-wrap and keep columns shorter than about 74 characters or
so.

That way "git log" and other tools will show things nicely even when
it's indented.

For Vim, 'set textwidth=x colorcolumn=x' can be useful here.

Consider explaining your solution and why you're doing what you're doing,
as opposed to only describing what you're doing.
Reviewers and your future self can read the commit, but might not
understand why a particular solution was implemented.

You may also choose to organize the body in a more structured way.

For example:

src/xyz/module_that_was_changed.rs:
  * using indentation and bullets/lists
  * to break down the description by file change

or

todo:
  1. adding
  2. todo
  3. items
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.