Sometimes it is needed to store compressed data in the DB. Unfortunately not all the DBs have built-in compression and FUSE compressed FSes are not available for every OS. So it may make sense to store compressed binary blobs in the DB.

Unfortunately when one sees them in DBeaver he sees them compressed, but often they are needed uncompressed. So it'd be nice to have a feature to decompress the

databasename can not contain dot 。if contain， after dot string will be discard。 i found like pattern in SQLServerDataSourceMetaData class "jdbc:(microsoft:)?sqlserver://([\w-.]+):?([0-9]);\S(DatabaseName|database)=([\w-]+);?" should be "jdbc:(microsoft:)?sqlserver://([\w-.]+):?([0-9]);\S(DatabaseName|database)=([\w-.]+);?"

Is this a bug or feature request?

FR

What is the current behavior?

not in the tree

What is the expected or desired behavior?

should be under the section "System"

Currently, the JDBC string containing the host name and port is hardcoded. For example, consider the connection string for MySQL:

https://github.com/sqlancer/sqlancer/blob/e62224edcb43fe421dc87601f75090739e34e595/src/sqlancer/mysql/MySQLProvider.java#L248

It would be desirable to make this configurable. We could provide an option to set the JDBC string for each DBMS. For example, for MySQL,

We don't want to build releases on any tags, just for releases

Monitoring is a paid  option in nginx (part of nginx plus), so providing a free Prometheus exporter will be appealing to many nginx users

Packaging this exporter comprises two sides:
a) RPM-based operating systems: look at any of the other exporters in OBS and adapt the .spec
b) Since Debian al

EntityManager should be improved with better documentation. All the undocumented GET APIs should also add the EntityOperationContext in their signature to enable future use (like the other APIs).