DatabaseOperations should handle connection failures gracefully

[leonibr]

Problem

The DatabaseOperations class currently throws unhandled PostgresException when database connections fail, which can cause application crashes and poor user experience in production environments.

Current Behavior

When the database is unavailable or authentication fails, the DatabaseOperations class throws exceptions like:

Npgsql.PostgresException (0x80004005): 28P01: 

This causes the entire caching operation to fail and can propagate up the call stack, potentially crashing the application.

Proposed Solution

Modify the DatabaseOperations class to handle connection failures gracefully

Implementation Considerations

• Maintain backward compatibility where possible