Releases
agents-v0.2.74
Compare
Sorry, something went wrong.
No results found
更新内容
access (0.1.34 → 0.1.35)
fix(dameng): handle DBMS_OUTPUT messages safely
bigquery (0.1.38 → 0.1.39)
fix(dameng): handle DBMS_OUTPUT messages safely
Apache Cassandra (0.1.37 → 0.1.38)
feat(cassandra): support HOCON Kerberos and Astra natively
feat(cassandra): complete native agent migration
feat(cassandra): add native Go agent
fix(dameng): handle DBMS_OUTPUT messages safely
dameng (0.1.42 → 0.1.43)
fix(dameng): handle DBMS_OUTPUT messages safely
fix(dameng): handle DBMS_OUTPUT messages safely
databend (0.1.25 → 0.1.26)
fix(dameng): handle DBMS_OUTPUT messages safely
databricks (0.1.32 → 0.1.33)
fix(dameng): handle DBMS_OUTPUT messages safely
db2 (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
etcd (0.1.25 → 0.1.26)
fix(dameng): handle DBMS_OUTPUT messages safely
exasol (0.1.32 → 0.1.33)
fix(dameng): handle DBMS_OUTPUT messages safely
firebird (0.1.32 → 0.1.33)
fix(dameng): handle DBMS_OUTPUT messages safely
gbase8a (0.1.32 → 0.1.33)
fix(dameng): handle DBMS_OUTPUT messages safely
gbase8s (0.1.26 → 0.1.27)
fix(dameng): handle DBMS_OUTPUT messages safely
goldendb (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
h2 (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
h2-legacy (0.1.7 → 0.1.8)
fix(dameng): handle DBMS_OUTPUT messages safely
highgo (0.1.35 → 0.1.36)
fix(dameng): handle DBMS_OUTPUT messages safely
hive (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
informix (0.1.38 → 0.1.39)
fix(dameng): handle DBMS_OUTPUT messages safely
iotdb (0.1.25 → 0.1.26)
fix(dameng): handle DBMS_OUTPUT messages safely
iris (0.1.28 → 0.1.29)
fix(dameng): handle DBMS_OUTPUT messages safely
人大金仓 KingbaseES (0.1.41 → 0.1.42)
fix(kingbase): cache metadata field capabilities
fix(dameng): handle DBMS_OUTPUT messages safely
kylin (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
mongodb (0.1.39 → 0.1.40)
fix(mongodb): support collation for find queries
fix(dameng): handle DBMS_OUTPUT messages safely
neo4j (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
oceanbase-oracle (0.1.33 → 0.1.34)
fix(dameng): handle DBMS_OUTPUT messages safely
Oracle (0.1.40 → 0.1.41)
fix(oracle): defer legacy LOB connection switch
fix(oracle): retry XMLTYPE queries after decode errors
fix(oracle): preserve quoted object names in DDL
fix(dameng): handle DBMS_OUTPUT messages safely
oscar (0.1.12 → 0.1.13)
fix(dameng): handle DBMS_OUTPUT messages safely
rocketmq (0.1.1 → 0.1.2)
feat(rocketmq): improve connections, topics, and message queries
fix(dameng): handle DBMS_OUTPUT messages safely
saphana (0.1.32 → 0.1.33)
fix(dameng): handle DBMS_OUTPUT messages safely
snowflake (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
spark (0.1.9 → 0.1.10)
fix(dameng): handle DBMS_OUTPUT messages safely
sqlserver-legacy (0.1.8 → 0.1.9)
fix(dameng): handle DBMS_OUTPUT messages safely
sundb (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
tdengine (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
teradata (0.1.32 → 0.1.33)
fix(dameng): handle DBMS_OUTPUT messages safely
trino (0.1.37 → 0.1.38)
fix(dameng): handle DBMS_OUTPUT messages safely
uxdb (0.1.4 → 0.1.5)
fix(dameng): handle DBMS_OUTPUT messages safely
Vastbase (0.1.37 → 0.1.38)
feat(vastbase): replace JDBC agent with native Go driver
fix(dameng): handle DBMS_OUTPUT messages safely
vertica (0.1.32 → 0.1.33)
fix(dameng): handle DBMS_OUTPUT messages safely
虚谷 XuguDB (0.1.27 → 0.1.28)
fix(xugu): recover metadata access for ordinary users
fix(dameng): handle DBMS_OUTPUT messages safely
yashandb (0.1.33 → 0.1.34)
fix(dameng): handle DBMS_OUTPUT messages safely
zookeeper (0.1.15 → 0.1.16)
fix(dameng): handle DBMS_OUTPUT messages safely
You can’t perform that action at this time.