Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Client Compatibility

This guide covers compatibility considerations and configuration steps for connecting various database clients to AngaraBase.

DBeaver

DBeaver is a popular database administration tool that can connect to AngaraBase via the PostgreSQL protocol. However, DBeaver automatically sends metadata queries to pg_catalog and information_schema tables that AngaraBase does not support, which can cause connection failures.

Problem

When connecting DBeaver to AngaraBase, you may encounter feature_not_supported errors. This happens because DBeaver automatically sends queries to PostgreSQL system catalogs (pg_catalog.* and information_schema.*) during connection setup and schema browsing. AngaraBase does not implement these PostgreSQL-specific metadata tables.

Solution

Follow these steps to configure DBeaver for AngaraBase compatibility:

1. Connection Properties

In DBeaver, edit your connection and go to Driver Properties:

  • Set assumeMinServerVersion = 9.0
  • Set preferQueryMode = simple

These settings reduce the number of metadata queries DBeaver sends.

2. PostgreSQL Connection Settings

In the PostgreSQL tab of your connection settings:

  • Uncheck “Read all data types”
  • Uncheck “Show non-default schemas”

This prevents DBeaver from querying system catalogs for type and schema information.

3. Server Type Selection

When creating the connection, select PostgreSQL 9.x as the server type. This uses a compatibility mode with minimal system catalog queries.

Diagnostics

If you’re still experiencing issues, you can enable slow query logging to see exactly what queries DBeaver is sending:

export ANGARABASE_LOG_MIN_DURATION_MS=0
export ANGARABASE_LOG_QUERY_TEXT=1

Start your AngaraBase server with these environment variables to log all queries. Check the logs to identify which specific queries are failing.

Alternative Approach

If the above configuration doesn’t work for your use case, consider using a simpler PostgreSQL client like psql for command-line access:

psql -h localhost -p 5152 -U your_username -d your_database

Limitations

Even with proper configuration, some DBeaver features may not work with AngaraBase:

  • Schema browser may show limited information
  • Auto-completion may be reduced
  • Some administrative features will not be available

For the most complete AngaraBase experience, consider using the native angara-cli tool or connecting via standard PostgreSQL drivers in your applications.

Other Clients

psql

The PostgreSQL command-line client works well with AngaraBase:

psql -h localhost -p 5152 -U username -d database_name

JDBC/ODBC Drivers

Standard PostgreSQL JDBC and ODBC drivers should work with AngaraBase for basic SQL operations. Avoid using driver features that query system catalogs.

Application Frameworks

Most application frameworks (Django, Rails, etc.) work with AngaraBase when configured to use PostgreSQL drivers, though some ORM introspection features may be limited.

Troubleshooting

Common Issues

IssueCauseSolution
feature_not_supported on connectionClient querying pg_catalogConfigure client to minimize metadata queries
Slow connection setupToo many system queriesUse preferQueryMode=simple
Missing schema informationAngaraBase doesn’t implement full pg_catalogUse direct SQL queries instead of client introspection

Getting Help

If you encounter client compatibility issues not covered here:

  1. Check the Known Issues page
  2. Enable query logging to identify problematic queries
  3. Consult the Support page for additional resources

For additional client-specific configuration tips, see our community documentation.

Дальше