Question 1

How do I use crystal-db with PostgreSQL in Crystal?

Accepted Answer

Add the crystal-pg driver to your shard.yml, require it in your code, and use DB.open with a PostgreSQL connection string. Use $1, $2 placeholders for parameters instead of ?, as shown in the README example.

Question 2

crystal-db vs direct driver: which is better for a simple SQLite app?

Accepted Answer

For a simple SQLite-only app, a direct driver like crystal-sqlite3 might be simpler with less overhead. crystal-db adds abstraction for portability, but if you don't need to switch databases, the direct approach avoids extra dependencies.

Question 3

Does crystal-db support connection pooling out of the box?

Accepted Answer

Yes, crystal-db includes built-in connection pooling, which is automatically managed when you use DB.open. This helps optimize database connections in concurrent applications without extra configuration.

Question 4

How to handle nested transactions in crystal-db?

Accepted Answer

Use the db.transaction block within another transaction block; crystal-db supports nested transactions as per the key features. Ensure your database driver also supports it, as implementation details may vary.

Question 5

What's the performance impact of using crystal-db over raw drivers?

Accepted Answer

crystal-db adds a thin abstraction layer, so performance overhead is minimal for most use cases. However, for blobs or high-throughput scenarios, direct driver access might be faster due to the lack of IO optimization noted in the roadmap.

Question 6

Can I use multiple database drivers in one Crystal project with crystal-db?

Accepted Answer

Yes, the README states that multiple drivers can be included in the same application. Just add each driver to shard.yml and require them as needed, allowing you to connect to different databases simultaneously.

crystal-db

What is crystal-db?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions