# Query (disambiguation)

The term "query" can mean multiple things: query-string as part of an URL sql-query to query a database

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## CVE-2026-77367 - Daptin: Unauthenticated SQL Injection via the \`sort\` query parameter on every entity list endpoint

DevFeed: [CVE-2026-77367 - Daptin: Unauthenticated SQL Injection via the \`sort\` query parameter on every entity list endpoint](<https://devfeed.tech/articles/cve-2026-77367-daptin-unauthenticated-sql-injection-via-the-sort-query-parameter-on-every-entity-list-endpoint-143947.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-77367>)

Author: CVEFEED.io; github.com

Published: 2026-11-19T17:18:59Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [SQL](<https://devfeed.tech/topics/sql.md>), [sql-database](<https://devfeed.tech/topics/sql-database.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [can](<https://devfeed.tech/tags/can.md>), [cms](<https://devfeed.tech/tags/cms.md>), [column](<https://devfeed.tech/tags/column.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-77367](<https://devfeed.tech/tags/cve-2026-77367.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [daptin](<https://devfeed.tech/tags/daptin.md>), [error](<https://devfeed.tech/tags/error.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [headless](<https://devfeed.tech/tags/headless.md>), [identifier](<https://devfeed.tech/tags/identifier.md>), [list](<https://devfeed.tech/tags/list.md>), [schema](<https://devfeed.tech/tags/schema.md>), [sort](<https://devfeed.tech/tags/sort.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-injection](<https://devfeed.tech/tags/sql-injection.md>)

### AI overview

Before Daptin 0.12.30, the generic GET /api/{entity} list endpoint accepts unvalidated, attacker-controlled `sort` values. In PaginatedFindAllWithoutFilters, those values are used to construct SELECT and ORDER BY identifiers without checking them against the table schema; an embedded quote can break out of the quoted identifier and alter SQL parsing. The excerpt says unauthenticated attackers may extract unauthorized table data through blind or error-based behavior, or repeatedly trigger query failures. The issue is fixed in version 0.12.30.

### Source excerpt

CVE ID :CVE-2026-77367 Published : Nov. 19, 2026, 5:18 p.m. | 26 minutes ago Description :Daptin is a GraphQL/JSON-API headless CMS. Prior to 0.12.30, the generic GET /api/{entity} list endpoint accepts attacker-controlled sort values in PaginatedFindAllWithoutFilters in server/resource/resource_findallpaginated.go without validating the requested column against the table schema. The code uses those values for SELECT and ORDER BY identifier construction, so an embedded identifier quote can terminate the quoted identifier and make the remainder parse as SQL, allowing an unauthenticated attacker to extract unauthorized table data through blind or error-based behavior or repeatedly trigger query failures. This issue is fixed in version 0.12.30. Severity: 9.4 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## How to use Amazon Aurora DSQL audit logs

DevFeed: [How to use Amazon Aurora DSQL audit logs](<https://devfeed.tech/articles/how-to-use-amazon-aurora-dsql-audit-logs-141385.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-to-use-amazon-aurora-dsql-audit-logs/>)

Author: Koji Shinkubo

Published: 2026-11-18T21:33:01Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [athena](<https://devfeed.tech/tags/athena.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-logging](<https://devfeed.tech/tags/audit-logging.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [configure](<https://devfeed.tech/tags/configure.md>), [database](<https://devfeed.tech/tags/database.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [field](<https://devfeed.tech/tags/field.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [post](<https://devfeed.tech/tags/post.md>), [query](<https://devfeed.tech/tags/query.md>), [records](<https://devfeed.tech/tags/records.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [s3](<https://devfeed.tech/tags/s3.md>), [sql](<https://devfeed.tech/tags/sql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Aurora DSQL audit logging records configured SQL statement classes and delivers records to S3; it is off until both a destination and recording settings are configured. The article describes role-based scope, including READ/SELECT, and a setup that separates audit administration from DBA permissions. Records can identify the IAM role and database role, transaction, statement, and optionally bound values and row counts. Athena can query the S3 logs, while CloudTrail connection events can be joined by session ID to add client IP information; transaction IDs can also link audit records to CDC changes. Limits and tradeoffs include potentially high log volume and charges, no table- or column-level scope, no client IP or success/failure field in audit records, and recording statements from rolled-back transactions. The article recommends testing scope and volume before production and protecting sensitive log content through access controls, encryption, and retention settings.

### Source excerpt

Amazon Aurora DSQL audit logging records the SQL statements that run in your database and delivers them to Amazon S3. This post shows how to configure audit logging to meet regulatory requirements, explains what each recorded field proves in an audit, and shows how to query the logs in Amazon S3 with Amazon Athena.

## The Agent Can Guess. The Query Engine Can't.

DevFeed: [The Agent Can Guess. The Query Engine Can't.](<https://devfeed.tech/articles/the-agent-can-guess-the-query-engine-can-t-141975.md>)

Original publisher: [Read original article](<https://www.starburst.io/blog/gpu-acceleration-gpu-native-engine-torin-the-agent-can-guess-the-query-engine-cant>)

Published: 2026-11-18T16:05:22Z

Content type: article

Language: en

Sources: [Starburst Data](<https://devfeed.tech/sources/starburst-data.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [AI response variability](<https://devfeed.tech/topics/ai-response-variability.md>), [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [added](<https://devfeed.tech/tags/added.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [application](<https://devfeed.tech/tags/application.md>), [can](<https://devfeed.tech/tags/can.md>), [engine](<https://devfeed.tech/tags/engine.md>), [query](<https://devfeed.tech/tags/query.md>), [query-engine](<https://devfeed.tech/tags/query-engine.md>), [question](<https://devfeed.tech/tags/question.md>)

### AI overview

Torin is Starburst's GPU-native SQL query engine, designed to accelerate analytical work while returning the same rows as CPU execution. Trino continues to parse, optimize, and schedule queries; Torin runs supported operators on NVIDIA GPUs, while unsupported work stays on the CPU in the same query. It preserves CPU-compatible behavior by analyzing expressions for failure risks--for example, avoiding division by zero when a filter condition guards a division--and choosing safe evaluation strategies. `EXPLAIN ANALYZE` shows where query work ran. Torin is best suited to large scans, joins, aggregations, AI data preparation, and text or pattern filters over Parquet tables in Apache Iceberg, Hive, or Delta Lake. It requires a supported NVIDIA GPU with at least 24 GB memory; 80 GB or more is recommended. `DISTINCT` in `SELECT`, user-defined functions, complex types, non-Parquet scans, and inter-worker exchanges remain on CPU. Performance gains vary from none to an order of magnitude; small or lightweight queries may not keep a GPU busy. Torin is in limited general availability for Starburst Enterprise.

### Source excerpt

Ask an AI agent the same question twice and you may get two different answers. ...

## 6 Things a Senior Engineer Covers When a Payment Is Retried

DevFeed: [6 Things a Senior Engineer Covers When a Payment Is Retried](<https://devfeed.tech/articles/6-things-a-senior-engineer-covers-when-a-payment-is-retried-138255.md>)

Original publisher: [Read original article](<https://thetshaped.dev/p/how-to-design-a-payments-endpoint-idempotency>)

Author: The T-Shaped Dev

Published: 2026-11-17T11:03:34Z

Content type: article

Language: en

Sources: [The T-Shaped Dev](<https://devfeed.tech/sources/the-t-shaped-dev.md>)

Topics: [payment-gateway](<https://devfeed.tech/topics/payment-gateway.md>), [stripe](<https://devfeed.tech/topics/stripe.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [Finance](<https://devfeed.tech/topics/finance.md>)

Tags: [adyen](<https://devfeed.tech/tags/adyen.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [astro](<https://devfeed.tech/tags/astro.md>), [async](<https://devfeed.tech/tags/async.md>), [backends](<https://devfeed.tech/tags/backends.md>), [call](<https://devfeed.tech/tags/call.md>), [card](<https://devfeed.tech/tags/card.md>), [charged](<https://devfeed.tech/tags/charged.md>), [charges](<https://devfeed.tech/tags/charges.md>), [charging](<https://devfeed.tech/tags/charging.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [click](<https://devfeed.tech/tags/click.md>), [client](<https://devfeed.tech/tags/client.md>), [cloudways](<https://devfeed.tech/tags/cloudways.md>), [cloudways-velocity](<https://devfeed.tech/tags/cloudways-velocity.md>), [crash](<https://devfeed.tech/tags/crash.md>), [key](<https://devfeed.tech/tags/key.md>), [order](<https://devfeed.tech/tags/order.md>), [payment](<https://devfeed.tech/tags/payment.md>)

### AI overview

A retry-safe payment flow anchors each attempt to a server-created order. A database partial unique index permits one live attempt per order; `INSERT ... ON CONFLICT DO NOTHING` chooses the winner, avoiding the race in check-then-insert. Commit the processing row before calling the provider. Retries and lease takeovers reuse the attempt's stored amount, card, and provider key, so a charge completed before a server crash can be replayed safely; declines release the order for a new attempt. Unknown outcomes stay processing, and expired leases are handled by later requests or a sweeper. Provider keys have retention limits: the excerpt says Stripe keeps them at least 24 hours, so older attempts require reconciliation rather than another charge attempt. Queue receipts and payment events with the success update in an outbox, whose database guard prevents duplicate effects even when email or webhook delivery retries.

### Source excerpt

Where the key comes from, one payment per order, the decline, the crash, the receipt, and what the interviewer grades.

## Tight Width Minimisation of Self-Join-Free Quantified Conjunctive Queries

DevFeed: [Tight Width Minimisation of Self-Join-Free Quantified Conjunctive Queries](<https://devfeed.tech/articles/tight-width-minimisation-of-self-join-free-quantified-conjunctive-queries-138303.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.20845>)

Author: Hubie Chen, Fabio Mogavero, Sam M. Thompson

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [cs-db](<https://devfeed.tech/tags/cs-db.md>), [cs-lo](<https://devfeed.tech/tags/cs-lo.md>), [databases](<https://devfeed.tech/tags/databases.md>), [queries](<https://devfeed.tech/tags/queries.md>), [query](<https://devfeed.tech/tags/query.md>)

### AI overview

For self-join-free quantified conjunctive queries, the minimum width reached through natural, established rewriting rules equals the minimum width among all logically equivalent first-order formulas. Here, width is the maximum number of free variables in any subformula. The result means width can be optimized for this query subclass with a rewriting algorithm that preserves logical equivalence.

### Source excerpt

arXiv:2611.20845v1 Announce Type: new Abstract: Query minimisation is a classical problem in database theory and the width of a formula, defined as the maximum number of free variables over all subformulae, is a central measure for query evaluation. We study width minimisation for a subclass of quantified conjunctive queries (QCQs), namely self-join-free QCQs. For this subclass, we show that rewriting optimality coincides with semantic optimality: given a query $\phi$, the minimum-width query obtainable from $\phi$ by applying natural and established rewriting rules has minimum width among all first-order formulae logically equivalent to $\phi$. As a consequence, the width of a self-join-free QCQ can be optimised by a logical-equivalence-preserving rewriting algorithm.

## Query Processing with eBPF-Offload on Computational Storage

DevFeed: [Query Processing with eBPF-Offload on Computational Storage](<https://devfeed.tech/articles/query-processing-with-ebpf-offload-on-computational-storage-135445.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18119>)

Author: Alexander Krause, Niclas Hedam, Johannes Pietrzyk, Dirk Habich, Wolfgang Lehner, Sangjin Lee, Alberto Lerner, Philippe Bonnet

Published: 2026-11-16T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [eBPF](<https://devfeed.tech/topics/ebpf.md>)

Tags: [cs-db](<https://devfeed.tech/tags/cs-db.md>), [databases](<https://devfeed.tech/tags/databases.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [execution](<https://devfeed.tech/tags/execution.md>), [query-processing](<https://devfeed.tech/tags/query-processing.md>), [storage](<https://devfeed.tech/tags/storage.md>)

### AI overview

Delilah tests whether standard computational storage is a good fit for query processing. It uses an open-hardware device that follows the NVMe and SNIA execution model: the host stages data in device memory, then invokes device functions encoded as eBPF. In an initial experiment, the authors hand-coded part of SSB Q3.3 for the device. They report little gain over host execution, column-at-a-time processing, and time spent staging and moving data in device memory. Since they attribute these obstacles to the execution model, they did not continue database integration and instead describe limitations to inform a different model for data-intensive workloads.

### Source excerpt

arXiv:2611.18119v1 Announce Type: new Abstract: The idea of pushing computation to storage devices has been explored for decades. In recent years, research has focused on computational storage, i.e., devices that allow a host to execute functions as I/O commands on local data. Today, the NVMe and SNIA computational storage standards share an execution model in which the host invokes functions on the device, on data that the host has moved into device memory. Both standards single out eBPF as a format for functions offloaded by the host. In this paper, we study whether this form of computational storage is a good match for query processing. We present the design and implementation of Delilah, a prototype based on an open-hardware device that implements the standard execution model on an actual device and runs eBPF programs calling device-resident functions. As an initial step, we hand-coded a portion of SSB Q3.3 for execution on the device, aiming to integrate computational storage with a database system's storage manager. The series of experiments that we ran showed that offloading gains little over host execution, execution degenerates into column-at-a-time processing, and time is spent staging and moving data in device memory. Because these roadblocks stem from the execution model rather than from the query, we did not pursue integration further. We detail these limitations and lay the groundwork for a different computational storage model better aligned with data-intensive workloads.

## CVE-2026-126196 - pgEdge Postgres MCP Server read-only mode can be bypassed by SQL statement smuggling through query\_database

DevFeed: [CVE-2026-126196 - pgEdge Postgres MCP Server read-only mode can be bypassed by SQL statement smuggling through query\_database](<https://devfeed.tech/articles/cve-2026-126196-pgedge-postgres-mcp-server-read-only-mode-can-be-bypassed-by-sql-statement-smuggling-through-query-database-130808.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-126196>)

Author: CVEFEED.io; github.com

Published: 2026-11-12T18:17:24Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [SQL](<https://devfeed.tech/topics/sql.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [availability](<https://devfeed.tech/tags/availability.md>), [cve-2026-126196](<https://devfeed.tech/tags/cve-2026-126196.md>), [database](<https://devfeed.tech/tags/database.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [pgedge](<https://devfeed.tech/tags/pgedge.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [sql](<https://devfeed.tech/tags/sql.md>), [transaction](<https://devfeed.tech/tags/transaction.md>)

### AI overview

Before version 1.1.0, pgEdge Postgres MCP Server could bypass `read_only` through `query_database`: unrecognized SQL sent via pgx Exec without bind parameters used PostgreSQL's simple query protocol, which accepts multiple semicolon-separated statements. When the connecting role had write privileges, a caller could combine transaction or session changes with database writes; pooled session state could also leave later calls writable. The issue could affect integrity and availability, but the description reports no added confidentiality impact beyond permitted reads. The issue is fixed in version 1.1.0.

### Source excerpt

CVE ID :CVE-2026-126196 Published : Nov. 12, 2026, 6:17 p.m. | 1 hour, 26 minutes ago Description :pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, query_database on a read_only connection could send unrecognized statements through pgx Exec without bind parameters, selecting PostgreSQL's simple query protocol and allowing multiple semicolon-separated statements in one request. A caller could combine transaction or session state changes with database writes, and pooled session state could leave later calls writable, when the connecting role held write privileges. The flaw affected deployments relying on read_only as a safety boundary, could compromise integrity and availability, and did not add confidentiality impact beyond the reads already permitted by the connection. This issue is fixed in 1.1.0. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Apache Iceberg Partition Statistics: compute\_partition\_stats, Pruning, and Query Planning

DevFeed: [Apache Iceberg Partition Statistics: compute\_partition\_stats, Pruning, and Query Planning](<https://devfeed.tech/articles/apache-iceberg-partition-statistics-compute-partition-stats-pruning-and-query-planning-123560.md>)

Original publisher: [Read original article](<https://www.dremio.com/blog/apache-iceberg-partition-statistics-compute_partition_stats-pruning-and-query-planning/>)

Author: Alex Merced

Published: 2026-11-09T13:42:02Z

Content type: article

Language: en

Sources: [Dremio](<https://devfeed.tech/sources/dremio.md>)

Topics: [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [table-partitioning](<https://devfeed.tech/topics/table-partitioning.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [compute](<https://devfeed.tech/tags/compute.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [dremio-blog-open-data-insights](<https://devfeed.tech/tags/dremio-blog-open-data-insights.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [partition](<https://devfeed.tech/tags/partition.md>), [planning](<https://devfeed.tech/tags/planning.md>), [pruning](<https://devfeed.tech/tags/pruning.md>)

### AI overview

Iceberg partition statistics summarize file metrics by partition for a specific snapshot; compute_partition_stats writes them to a metadata file referenced by that snapshot, without rewriting data files or creating separate Puffin column statistics. Incremental runs can reduce work when few manifests change, though manifest churn may force rescans and missing file-level metrics limit the summaries. Planner support varies by engine and version, so verify snapshot freshness and compare EXPLAIN estimates, partitions and files scanned, bytes read, and query time before and after refresh. These statistics help most when partition keys match common filters; they do not replace file-level pruning for non-partition columns or fix a mismatched partition layout. The example Spark procedure signature and parallelism settings may vary by release.

### Source excerpt

Compute Iceberg partition statistics incrementally, understand their metadata model, validate pruning, and separate them from column NDV statistics. The post Apache Iceberg Partition Statistics: compute_partition_stats, Pruning, and Query Planning appeared first on Dremio.

## ZDI-26-891: Philips Hue Bridge Pro SQL Injection Remote Code Execution Vulnerability

DevFeed: [ZDI-26-891: Philips Hue Bridge Pro SQL Injection Remote Code Execution Vulnerability](<https://devfeed.tech/articles/zdi-26-891-philips-hue-bridge-pro-sql-injection-remote-code-execution-vulnerability-121850.md>)

Original publisher: [Read original article](<http://www.zerodayinitiative.com/advisories/ZDI-26-891/>)

Published: 2026-11-06T06:00:00Z

Content type: news

Language: en

Sources: [Zero Day Initiative](<https://devfeed.tech/sources/zero-day-initiative.md>)

Topics: [Exploit](<https://devfeed.tech/topics/exploit.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [philips](<https://devfeed.tech/tags/philips.md>), [pro](<https://devfeed.tech/tags/pro.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [remote-code-execution-vulnerability](<https://devfeed.tech/tags/remote-code-execution-vulnerability.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-injection](<https://devfeed.tech/tags/sql-injection.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

ZDI-26-891 describes a SQL injection flaw in the Philips Hue Bridge Pro HTTP service, which listens on TCP port 443 by default. A network-adjacent attacker can bypass the required authentication mechanism and exploit an unvalidated user-supplied string used to construct SQL queries, enabling arbitrary code execution as root. ZDI assigns CVSS 8.0 and identifies CVE-2026-118632. The advisory says the issue is fixed in Bridge Pro firmware 6.1.2071524030 or later.

### Source excerpt

This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Philips Hue Bridge Pro. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The ZDI has assigned a CVSS rating of 8.0. The following CVEs are assigned: CVE-2026-118632.

## Monus vs. Interpretations in Semiring Semantics

DevFeed: [Monus vs. Interpretations in Semiring Semantics](<https://devfeed.tech/articles/monus-vs-interpretations-in-semiring-semantics-121012.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.08474>)

Author: Phokion G. Kolaitis

Published: 2026-11-06T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [SQL](<https://devfeed.tech/topics/sql.md>)

Tags: [cs-db](<https://devfeed.tech/tags/cs-db.md>), [databases](<https://devfeed.tech/tags/databases.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [queries](<https://devfeed.tech/tags/queries.md>), [query-languages](<https://devfeed.tech/tags/query-languages.md>), [semantics](<https://devfeed.tech/tags/semantics.md>)

### AI overview

The canonical-interpretation and compatible-interpretation semantics for first-order formulas in negation normal form cannot express the monus operation on semiring-annotated relations when annotations use the bag, tropical, or fuzzy semiring. The authors conclude that these interpretation-based semantics therefore cannot capture SQL semantics. The supplied text states this result but provides no proof details.

### Source excerpt

arXiv:2611.08474v1 Announce Type: new Abstract: Interpretations have been widely used in the study of provenance of queries on semiring-annotated databases. Here, we consider two different interpretation-based semantics for first-order formulas in negation normal form, namely, the canonical-interpretation semantics and the compatible-interpretation semantics. We show that the resulting query languages cannot express the monus operation on semiring-annotated relations, when the annotations come from the bag semiring or the tropical semiring or the fuzzy semiring. Consequently, the semantics of SQL cannot be captured using the interpretation-based semantics considered here.

## CVE-2026-97377 - SuiteCRM: Authenticated SQL Injection in SOAP Portal Method portal\_get\_entry\_list

DevFeed: [CVE-2026-97377 - SuiteCRM: Authenticated SQL Injection in SOAP Portal Method portal\_get\_entry\_list](<https://devfeed.tech/articles/cve-2026-97377-suitecrm-authenticated-sql-injection-in-soap-portal-method-portal-get-entry-list-119530.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-97377>)

Author: CVEFEED.io; github.com

Published: 2026-11-05T19:17:29Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [SQL](<https://devfeed.tech/topics/sql.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [blind](<https://devfeed.tech/tags/blind.md>), [crm](<https://devfeed.tech/tags/crm.md>), [customer-relationship-management](<https://devfeed.tech/tags/customer-relationship-management.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-97377](<https://devfeed.tech/tags/cve-2026-97377.md>), [database](<https://devfeed.tech/tags/database.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [issue](<https://devfeed.tech/tags/issue.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-injection](<https://devfeed.tech/tags/sql-injection.md>)

### AI overview

Before SuiteCRM 7.15.2 and 8.10.2, the legacy SOAP portal method portal_get_entry_list passes caller-controlled where and order_by values into SQL construction without sufficient neutralization. A low-privileged portal API user can exploit this for blind SQL injection to disclose database metadata and sensitive records, alter query behavior, or consume resources. The issue is fixed in versions 7.15.2 and 8.10.2.

### Source excerpt

CVE ID :CVE-2026-97377 Published : Nov. 5, 2026, 7:17 p.m. | 1 hour, 51 minutes ago Description :SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, the legacy SOAP portal method portal_get_entry_list propagates caller-controlled where and order_by values into SQL query construction without sufficient neutralization. A low-privileged portal API user can perform blind SQL injection to disclose database metadata and sensitive records, affect query behavior, and consume resources. This issue is fixed in versions 7.15.2 and 8.10.2. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## AvalancheBench: Evaluating Enterprise Agent-Driven Semantic Query Processing Through Latent World Recovery

DevFeed: [AvalancheBench: Evaluating Enterprise Agent-Driven Semantic Query Processing Through Latent World Recovery](<https://devfeed.tech/articles/avalanchebench-evaluating-enterprise-agent-driven-semantic-query-processing-through-latent-world-recovery-118105.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2605.24183>)

Author: Darek Kleczek, Fuheng Zhao, Alexander W. Lee, Julien Tissier, Pawel Liskowski, Ugur Cetintemel, Anupam Datta

Published: 2026-11-05T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-harnesses](<https://devfeed.tech/tags/agent-harnesses.md>), [agents](<https://devfeed.tech/tags/agents.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [avalanche](<https://devfeed.tech/tags/avalanche.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [cause](<https://devfeed.tech/tags/cause.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cortex](<https://devfeed.tech/tags/cortex.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-db](<https://devfeed.tech/tags/cs-db.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [data](<https://devfeed.tech/tags/data.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [query](<https://devfeed.tech/tags/query.md>), [query-processing](<https://devfeed.tech/tags/query-processing.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [world](<https://devfeed.tech/tags/world.md>)

### AI overview

AvalancheBench evaluates whether data agents can use semantic query operators effectively in end-to-end enterprise analysis. Its three validated tasks contain 58 questions across text, images, and documents, grouped into briefs where shared intermediate results can spread errors. In tests of five model-harness configurations across three agent harnesses using Snowflake Cortex AISQL, the best macro analytical fidelity was 0.82. The largest reported loss came from misinterpreting requirements (51.5%); failing to recover facts requiring semantic computation accounted for 45.1%, while misusing or avoiding operators accounted for 36.3% and incorrect operator outputs for 2.5%. Reusing results across questions contributed 29% of lost points. The benchmark tracks fidelity, monetary cost, and capability-adjusted token cost (CATC); monetary cost and CATC yielded different Pareto frontiers. These findings are limited to the evaluated tasks and configurations.

### Source excerpt

arXiv:2605.24183v2 Announce Type: replace Abstract: As LLMs improve, data agents are emerging as a new interface for analytics, while semantic query processing engines use LLMs to operate over structured and unstructured data. Existing benchmarks largely evaluate agents and semantic query engines in isolation, leaving it unclear whether agents can decide when and how to use semantic operators in end-to-end analysis. We introduce AvalancheBench, a multimodal enterprise analytics benchmark that generates observed data from latent world specifications and evaluates data agents on their ability to recover that world. The benchmark's 3 validated tasks contain 58 questions spanning text, images, and documents. Questions are provided together as a multi-part analytical brief and may share intermediate results, exposing the avalanche effect: errors can propagate through legitimate dependencies, and inappropriate reuse can cause otherwise unrelated questions to fail. AvalancheBench measures analytical fidelity, monetary cost, and capability-adjusted token cost (CATC), a new metric that weights token use by model capability to separate technical efficiency from provider pricing. We evaluate 5 model-harness configurations across 3 agent harnesses using Snowflake Cortex AISQL as the engine, with the best configuration reaching macro analytical fidelity of 0.82. Agents fail primarily in constructing the analysis: failing to recover facts that require semantic computation costs 45.1% of lost points, yet incorrect operator outputs account for only 2.5%, versus 36.3% from agents misusing or avoiding semantic operators. Misinterpreting requirements costs the most, at 51.5%. Errors also spread between questions: 29% of lost points come from reusing another question's results. Finally, monetary cost and CATC produce different Pareto frontiers, distinguishing economically attractive configurations from those that are technically resource efficient.

## There are things with ranks, but it's not always clear what the ranks mean

DevFeed: [There are things with ranks, but it's not always clear what the ranks mean](<https://devfeed.tech/articles/there-are-things-with-ranks-but-it-s-not-always-clear-what-the-ranks-mean-118976.md>)

Original publisher: [Read original article](<https://devblogs.microsoft.com/oldnewthing/20261104-00/?p=112830/>)

Author: Raymond Chen

Published: 2026-11-04T15:00:00Z

Content type: article

Language: en

Sources: [Raymond Chen](<https://devfeed.tech/sources/raymond-chen.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [api](<https://devfeed.tech/tags/api.md>), [code](<https://devfeed.tech/tags/code.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [driver](<https://devfeed.tech/tags/driver.md>), [feature](<https://devfeed.tech/tags/feature.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [old-new-thing](<https://devfeed.tech/tags/old-new-thing.md>)

### AI overview

The post shows how documentation can leave "rank" undefined, then explains the Windows package graph's actual ordering: packages are searched in ascending rank, so lower ranks have precedence. A process's graph starts empty; declared dependencies are added at rank zero in static resolution order. `AddPackageDependency` inserts a package after lower-ranked packages and before higher-ranked ones. By default, it follows packages with the same rank; `AddPackageDependencyOptions_PrependIfRankCollision` places it before them. Because rank is a signed integer, a negative rank can place a package ahead of the static dependencies. The post contrasts this unclear documentation with SQL Server full-text search, where higher rank explicitly means a more relevant match, and filter-driver altitude, where lower numerical altitude means loading lower in the I/O stack.

### Source excerpt

The problem with documentation written by people who know the feature too well. The post There are things with ranks, but it's not always clear what the ranks mean appeared first on The Old New Thing.

## Navigating Runtime Dynamism in Semantic Query Serving

DevFeed: [Navigating Runtime Dynamism in Semantic Query Serving](<https://devfeed.tech/articles/navigating-runtime-dynamism-in-semantic-query-serving-115959.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.04248>)

Author: Hengrui Zhang, Xupeng Miao

Published: 2026-11-04T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [batch](<https://devfeed.tech/tags/batch.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-db](<https://devfeed.tech/tags/cs-db.md>), [framework](<https://devfeed.tech/tags/framework.md>), [inference](<https://devfeed.tech/tags/inference.md>), [latency](<https://devfeed.tech/tags/latency.md>), [llm](<https://devfeed.tech/tags/llm.md>), [operator](<https://devfeed.tech/tags/operator.md>), [operators](<https://devfeed.tech/tags/operators.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [plan](<https://devfeed.tech/tags/plan.md>), [processing](<https://devfeed.tech/tags/processing.md>), [queries](<https://devfeed.tech/tags/queries.md>), [query](<https://devfeed.tech/tags/query.md>), [query-optimization](<https://devfeed.tech/tags/query-optimization.md>), [query-processing](<https://devfeed.tech/tags/query-processing.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [schedules](<https://devfeed.tech/tags/schedules.md>), [scheduling](<https://devfeed.tech/tags/scheduling.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [serving](<https://devfeed.tech/tags/serving.md>)

### AI overview

SeqoFlow addresses a feedback problem in serving concurrent LLM-powered semantic queries: scheduling needs estimates of remaining LLM work, while that work changes with runtime query plans. It decomposes queries into fine-grained units, enumerates equivalent plans subject to operator dependencies, and uses lightweight speculative cost estimates to guide both plan adaptation and scheduling. Batch-boundary preemption enables safe adaptation during execution. The abstract reports lower end-to-end latency than existing semantic query systems, adaptive query processing techniques, and conventional scheduling policies across varied query structures, data distributions, and arrival rates; it does not provide specific measurements.

### Source excerpt

arXiv:2611.04248v1 Announce Type: new Abstract: LLM-powered semantic queries increasingly combine relational processing with multiple LLM-based operators over unstructured data. Efficiently serving such queries is challenging due to runtime dynamism at two coupled levels. Across queries, dynamic arrivals and heterogeneous resource demands continuously change scheduling priorities. Within a query, heterogeneous characteristics across fine-grained input batches cause operator costs and selectivities to vary throughout execution, making a statically optimized plan unreliable. These two forms of dynamism create a circular dependency: inter-query scheduling requires estimates of remaining LLM work, while the remaining work depends on runtime plan choices whose costs become observable only during execution. We present SeqoFlow, a runtime framework that jointly adapts query plans and schedules concurrent semantic queries. SeqoFlow enumerates equivalence-preserving plan alternatives under operator dependencies and decomposes queries into fine-grained units, enabling safe plan adaptation and query preemption at batch boundaries. To support both decisions without exhaustively profiling candidate plans on the target LLM, SeqoFlow uses lightweight speculative estimation to capture runtime costs. These estimates jointly guide plan adaptation and inter-query scheduling, closing the loop between query optimization and LLM inference. Experiments across diverse query structures, data distributions, and arrival rates show that SeqoFlow substantially reduces end-to-end latency compared to existing semantic query systems, adaptive query processing techniques, and conventional scheduling policies.

## How to insert, query, and modify data in PostgreSQL (getting started with PostgreSQL, part three)

DevFeed: [How to insert, query, and modify data in PostgreSQL (getting started with PostgreSQL, part three)](<https://devfeed.tech/articles/how-to-insert-query-and-modify-data-in-postgresql-getting-started-with-postgresql-part-three-113441.md>)

Original publisher: [Read original article](<https://www.red-gate.com/simple-talk/databases/postgresql/how-to-insert-query-and-modify-data-in-postgresql-getting-started-with-postgresql-part-three/>)

Author: Grant Fritchey

Published: 2026-11-02T12:00:00Z

Content type: tutorial

Language: en

Sources: [Simple Talk](<https://devfeed.tech/sources/simple-talk.md>)

Topics: [CRUD](<https://devfeed.tech/topics/crud.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [aliases](<https://devfeed.tech/tags/aliases.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [database-administration](<https://devfeed.tech/tags/database-administration.md>), [databases](<https://devfeed.tech/tags/databases.md>), [delete](<https://devfeed.tech/tags/delete.md>), [examples](<https://devfeed.tech/tags/examples.md>), [featured](<https://devfeed.tech/tags/featured.md>), [getting-started](<https://devfeed.tech/tags/getting-started.md>), [gettingstartedpostgresgrant](<https://devfeed.tech/tags/gettingstartedpostgresgrant.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [insert](<https://devfeed.tech/tags/insert.md>), [join](<https://devfeed.tech/tags/join.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [query](<https://devfeed.tech/tags/query.md>), [select](<https://devfeed.tech/tags/select.md>), [sql](<https://devfeed.tech/tags/sql.md>), [t-sql-programming](<https://devfeed.tech/tags/t-sql-programming.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

The guide demonstrates PostgreSQL's basic data workflow: use INSERT to add rows, omitting IDENTITY columns or supplying DEFAULT so PostgreSQL can generate values; use SELECT with explicit columns and a schema-qualified table for clearer, controlled results; and filter or combine data with WHERE and JOIN. JOIN defaults to INNER JOIN, while LEFT and RIGHT joins return NULLs for nonmatching rows; aliases shorten table references. ORDER BY is needed for predictable ordering, especially with LIMIT. UPDATE and DELETE affect one table at a time and can use other tables for filtering; without WHERE they affect all matching rows in that table. Foreign keys can prevent deleting referenced rows. Under MVCC, changed or removed rows are logically deleted, with VACUUM later cleaning them up. The excerpt also gives container steps for launching the Bluebox sample database.

### Source excerpt

Learn how to insert, query, update, and delete data in PostgreSQL with real examples covering INSERT, SELECT, JOIN, WHERE, and more.... The post How to insert, query, and modify data in PostgreSQL (getting started with PostgreSQL, part three) appeared first on Simple Talk.

## Agent demand can't be forecast, meaning the database has to be ready for anything

DevFeed: [Agent demand can't be forecast, meaning the database has to be ready for anything](<https://devfeed.tech/articles/agent-demand-can-t-be-forecast-meaning-the-database-has-to-be-ready-for-anything-110719.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/01/agentic-ai-architecture-demands-real-time-databases-evolve26/>)

Author: Ryan Stevens

Published: 2026-11-01T14:25:39Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [AI-Ready Data](<https://devfeed.tech/topics/ai-ready-data.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-ai-architecture](<https://devfeed.tech/tags/agentic-ai-architecture.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-anywhere](<https://devfeed.tech/tags/ai-anywhere.md>), [ai-architecture](<https://devfeed.tech/tags/ai-architecture.md>), [ai-automation](<https://devfeed.tech/tags/ai-automation.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-return-on-investment](<https://devfeed.tech/tags/ai-return-on-investment.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [big-data](<https://devfeed.tech/tags/big-data.md>), [cloudera](<https://devfeed.tech/tags/cloudera.md>), [cloudera-anywhere](<https://devfeed.tech/tags/cloudera-anywhere.md>), [cube-event-coverage](<https://devfeed.tech/tags/cube-event-coverage.md>), [data-governance](<https://devfeed.tech/tags/data-governance.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [data-management](<https://devfeed.tech/tags/data-management.md>), [data-sovereignty](<https://devfeed.tech/tags/data-sovereignty.md>), [database](<https://devfeed.tech/tags/database.md>), [demand](<https://devfeed.tech/tags/demand.md>), [digital-transformation](<https://devfeed.tech/tags/digital-transformation.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [enterprise-data-platforms](<https://devfeed.tech/tags/enterprise-data-platforms.md>), [evolve26](<https://devfeed.tech/tags/evolve26.md>), [evolve2626eventpage](<https://devfeed.tech/tags/evolve2626eventpage.md>), [forecast](<https://devfeed.tech/tags/forecast.md>), [hybrid-cloud](<https://devfeed.tech/tags/hybrid-cloud.md>), [multicloud](<https://devfeed.tech/tags/multicloud.md>), [news](<https://devfeed.tech/tags/news.md>), [paul-gillin](<https://devfeed.tech/tags/paul-gillin.md>), [private-ai](<https://devfeed.tech/tags/private-ai.md>), [ross-armstrong](<https://devfeed.tech/tags/ross-armstrong.md>), [sovereign-ai](<https://devfeed.tech/tags/sovereign-ai.md>), [thecube](<https://devfeed.tech/tags/thecube.md>)

### AI overview

Agent workloads can send thousands of unpredictable, simultaneous queries across databases while still requiring millisecond responses, a demand PhoenixAI's sales VP says established database players struggle to meet for real-time analytics and customer SLAs. PhoenixAI's columnar engine is described as handling structured and unstructured data and determining how to answer queries as they arrive. Its self-managed PhoenixAI Anywhere can run in a customer's cloud, on premises, or in air-gapped environments; PhoenixAI is also available through Cloudera's marketplace. The planned AgentBase context environment is intended to restrict agents to needed data and provide governance guardrails. The excerpt says agents do not have to run on PhoenixAI.

### Source excerpt

Enterprises building an agentic AI architecture are learning that the database matters as much as the model. AI agents fire off thousands of unplanned queries at once -- and expect answers in milliseconds. PhoenixAI, the trade name of CelerData Inc., raised $80 million this year to develop database technology for AI agents to solve this [...] The post Agent demand can't be forecast, meaning the database has to be ready for anything appeared first on SiliconANGLE.

## Explorer and Notebooks: investigations your team can rerun

DevFeed: [Explorer and Notebooks: investigations your team can rerun](<https://devfeed.tech/articles/explorer-and-notebooks-investigations-your-team-can-rerun-109685.md>)

Original publisher: [Read original article](<https://supabase.com/blog/explorer-and-notebooks-investigations-your-team-can-rerun>)

Author: Wen Bo Xie; Joshen Lim; Saxon Fletcher; Charis Lam

Published: 2026-10-30T07:00:00Z

Content type: release

Language: en

Sources: [Supabase](<https://devfeed.tech/sources/supabase-blog.md>)

Topics: [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [jupyter](<https://devfeed.tech/topics/jupyter.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [beta](<https://devfeed.tech/tags/beta.md>), [branch](<https://devfeed.tech/tags/branch.md>), [cells](<https://devfeed.tech/tags/cells.md>), [change](<https://devfeed.tech/tags/change.md>), [charts](<https://devfeed.tech/tags/charts.md>), [database](<https://devfeed.tech/tags/database.md>), [editor](<https://devfeed.tech/tags/editor.md>), [explorer](<https://devfeed.tech/tags/explorer.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [investigations](<https://devfeed.tech/tags/investigations.md>), [logs](<https://devfeed.tech/tags/logs.md>), [notebook](<https://devfeed.tech/tags/notebook.md>), [project](<https://devfeed.tech/tags/project.md>), [run](<https://devfeed.tech/tags/run.md>), [save](<https://devfeed.tech/tags/save.md>), [supabase](<https://devfeed.tech/tags/supabase.md>), [supabase-database](<https://devfeed.tech/tags/supabase-database.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

Supabase Explorer brings database and log queries into one dashboard editor, where results can appear as tables or charts; log queries have their own time range. Notebooks combine saved queries, logic, charts, and markdown notes, but store queries rather than results, so rerunning them fetches current data. Teams can rerun investigations after changes, and keep notebooks in the `supabase` folder for versioning and review: create them in the dashboard and pull them with the CLI, or author locally and push them to the dashboard. Supabase Assistant can draft or edit notebook cells, but each create or edit requires approval and exposes readable SQL and markdown; Assistant use is optional. Explorer is in feature preview, while the CLI notebook commands are beta.

### Source excerpt

Explorer is one editor for your Supabase database and your logs. Save an investigation as a Notebook and anyone on the project can run it again.

## What the Heck is Hardcharger?

DevFeed: [What the Heck is Hardcharger?](<https://devfeed.tech/articles/what-the-heck-is-hardcharger-107729.md>)

Original publisher: [Read original article](<https://hackernoon.com/what-the-heck-is-hardcharger?source=rss>)

Author: Shawn Gordon

Published: 2026-10-30T05:48:03Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [DuckDB](<https://devfeed.tech/topics/duckdb.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [apache-arrow](<https://devfeed.tech/topics/apache-arrow.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [cURL](<https://devfeed.tech/topics/curl.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Deno](<https://devfeed.tech/topics/deno.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [admin](<https://devfeed.tech/tags/admin.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [apache-2-0](<https://devfeed.tech/tags/apache-2-0.md>), [apache-arrow](<https://devfeed.tech/tags/apache-arrow.md>), [arrow](<https://devfeed.tech/tags/arrow.md>), [audit](<https://devfeed.tech/tags/audit.md>), [chargewire-protocol](<https://devfeed.tech/tags/chargewire-protocol.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [duckdb](<https://devfeed.tech/tags/duckdb.md>), [duckdb-2-0](<https://devfeed.tech/tags/duckdb-2-0.md>), [gizmosql-successor](<https://devfeed.tech/tags/gizmosql-successor.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [hardcharger-explained](<https://devfeed.tech/tags/hardcharger-explained.md>), [http](<https://devfeed.tech/tags/http.md>), [license](<https://devfeed.tech/tags/license.md>), [license-keys](<https://devfeed.tech/tags/license-keys.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [server](<https://devfeed.tech/tags/server.md>), [sql](<https://devfeed.tech/tags/sql.md>)

### AI overview

Hardcharger is an Apache 2.0 DuckDB 2.0 server that replaces GizmoSQL with a from-scratch implementation and includes features that previously required GizmoSQL Enterprise licenses. Its Chargewire protocol carries Apache Arrow IPC data over ordinary HTTP/1.1 and TLS, with JSON control messages; it supports one-request short queries, asynchronous long queries, resumable downloads, and parallel result partitions. The article contrasts this with Arrow Flight SQL's gRPC transport, which the author says caused proxy and load-balancer problems and requires generated client code. Hardcharger's described security includes identity-bound handles, bearer tokens, OIDC and certificate authentication, plan-based access checks, and blocking access to sensitive host files. Included capabilities also cover granular roles and grants, row policies, masking, audit logs, monitoring, query controls, a web UI, and drivers for several languages. The author reports using its cloud service to share a DuckDB file and query it through an AI/MCP integration with a read-only token. Automatic startup on requests and running data collection apps on the server are described as desired future features.

### Source excerpt

Hardcharger is GizmoData's open-source DuckDB 2.0 server, built on Warp SQL, an HTTP protocol streaming Apache Arrow. Every feature included; no license keys.

## Under the Hood: How Room 3.0 and SQLDelight 2.x Detect Database Changes

DevFeed: [Under the Hood: How Room 3.0 and SQLDelight 2.x Detect Database Changes](<https://devfeed.tech/articles/under-the-hood-how-room-3-0-and-sqldelight-2-x-detect-database-changes-107102.md>)

Original publisher: [Read original article](<https://proandroiddev.com/under-the-hood-how-room-3-0-and-sqldelight-2-x-detect-database-changes-51e7a9b716dc?source=rss----c72404660798---4>)

Author: chanzmao

Published: 2026-10-29T17:35:32Z

Content type: comparison

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [sqldelight](<https://devfeed.tech/topics/sqldelight.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [changes](<https://devfeed.tech/tags/changes.md>), [database](<https://devfeed.tech/tags/database.md>), [flow](<https://devfeed.tech/tags/flow.md>), [kotlin-coroutines](<https://devfeed.tech/tags/kotlin-coroutines.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [query](<https://devfeed.tech/tags/query.md>), [room](<https://devfeed.tech/tags/room.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [sqldelight](<https://devfeed.tech/tags/sqldelight.md>), [tables](<https://devfeed.tech/tags/tables.md>)

### AI overview

Room 3.0 observes table invalidations: its Flow runs the query when collection starts, then reruns it after a relevant table change. This can rerun a query even when its result is unchanged; cancellation stops the observation. SQLDelight 2.x attaches a listener to a Query. `Query.asFlow()` emits the query as a notification, while downstream operators such as `mapToList()` execute SQL and fetch rows; listener cleanup occurs when collection closes or is cancelled. Neither mechanism avoids reading from the database after a relevant notification. The text cautions that SQLDelight's query-level listener does not guarantee fewer executions or prove that only affected queries are notified; behavior depends on notification and driver implementation details.

### Source excerpt

Room and SQLDelight both let us observe database queries as Kotlin Flows. When the underlying data changes, the Flow emits an update, allowing the UI to react without manually refreshing the data. Image created by AI The result looks similar from the outside, but the two libraries handle change notifications differently. Room relies on InvalidationTracker to monitor database tables. SQLDelight uses listeners attached to individual Query objects. Let's look at how these mechanisms work internally and what the differences mean in practice. How Room 3.0 Monitors Database Changes Room uses InvalidationTracker to keep track of changes to database tables. When a DAO query returns a Flow, Room uses this mechanism to determine when the query should run again. The important detail is that Room tracks which tables a query depends on, rather than tracking changes to the query result itself. What happens behind the scenes? The following example illustrates the basic idea. It is simplified pseudocode, not Room's actual implementation. fun <T> createRoomQueryFlow( tracker: InvalidationTracker, tables: Array<String>, queryBlock: suspend () -> T ): Flow<T> = flow { emit(queryBlock()) tracker.createFlow(*tables).collect { emit(queryBlock()) } } There are two things worth noting here. The query runs before change monitoring begins. When collection starts, queryBlock() fetches the current data and emits the result. The Flow then observes invalidation events from InvalidationTracker. A table change can trigger another query execution. Suppose a query reads from the users table. When Room detects a relevant change to that table, the Flow can emit another result by executing the query again. Room does not need to compare the old and new query results. It uses table invalidation as a signal that the result may have changed. This approach keeps the mechanism straightforward, but it has a trade-off: a change to a table can trigger re-execution even when the actual result of a particular que

## Little's Law Says Part of Your Sales Pipeline Is Dead. Here's the SQL to Find It.

DevFeed: [Little's Law Says Part of Your Sales Pipeline Is Dead. Here's the SQL to Find It.](<https://devfeed.tech/articles/little-s-law-says-part-of-your-sales-pipeline-is-dead-here-s-the-sql-to-find-it-106125.md>)

Original publisher: [Read original article](<https://hackernoon.com/littles-law-says-part-of-your-sales-pipeline-is-dead-heres-the-sql-to-find-it?source=rss>)

Author: Malek Damiri

Published: 2026-10-29T08:02:06Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [DuckDB](<https://devfeed.tech/topics/duckdb.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>)

Tags: [data-analytics](<https://devfeed.tech/tags/data-analytics.md>), [duckdb](<https://devfeed.tech/tags/duckdb.md>), [little](<https://devfeed.tech/tags/little.md>), [operations-research](<https://devfeed.tech/tags/operations-research.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [revops](<https://devfeed.tech/tags/revops.md>), [sales](<https://devfeed.tech/tags/sales.md>), [sales-operations](<https://devfeed.tech/tags/sales-operations.md>), [sales-pipeline](<https://devfeed.tech/tags/sales-pipeline.md>), [sql](<https://devfeed.tech/tags/sql.md>), [startups](<https://devfeed.tech/tags/startups.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>)

### AI overview

Little's Law (open deals ~= deals created per week x average weeks to resolution) can flag pipeline buildup that ordinary CRM value counts conceal. In the article's simulated data, a clean CRM has 190 open deals against 183 expected; when 15% of lost deals remain open, it has 510 against 182. The author then uses the 90th percentile of resolved-deal cycle time to group open deals by age: $6.4 million of $11.8 million is more than twice that threshold, versus one deal in the clean CRM's oldest bucket. Suggested steps are to exclude deals older than 2x p90 from coverage unless requalified with a dated next step, report expected versus actual open deals monthly, and track deals resolved per week. The check assumes a reasonably stable system; sudden volume changes add noise, and cycle time from closed deals may understate W if sales cycles are lengthening. Treat it as a diagnostic, then inspect the deals.

### Source excerpt

Malek Damiri applies Little's Law (L = λW) from warehouse operations to a sales pipeline to measure dead deals, with SQL you can run in DuckDB.

## Bringing the Big Ducks

DevFeed: [Bringing the Big Ducks](<https://devfeed.tech/articles/bringing-the-big-ducks-105858.md>)

Original publisher: [Read original article](<https://motherduck.com/blog/bigger-ducks>)

Author: Jordan Tigani

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [MotherDuck](<https://devfeed.tech/sources/motherduck.md>)

Topics: [DuckDB](<https://devfeed.tech/topics/duckdb.md>), [big-data](<https://devfeed.tech/topics/big-data.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [Ground truth / benchmark quality](<https://devfeed.tech/topics/ground-truth-benchmark-quality.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [arithmetic](<https://devfeed.tech/tags/arithmetic.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-synapse](<https://devfeed.tech/tags/azure-synapse.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarking](<https://devfeed.tech/tags/benchmarking.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [bigquery](<https://devfeed.tech/tags/bigquery.md>), [claude](<https://devfeed.tech/tags/claude.md>), [client](<https://devfeed.tech/tags/client.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cpus](<https://devfeed.tech/tags/cpus.md>), [data-warehouse](<https://devfeed.tech/tags/data-warehouse.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [duckdb](<https://devfeed.tech/tags/duckdb.md>), [motherduck](<https://devfeed.tech/tags/motherduck.md>)

### AI overview

MotherDuck's results suggest its single-node Giga instance can handle TPC-DS workloads at 1 TB and 10 TB scale while remaining competitive with distributed warehouses. On DuckDB 1.5.6, Giga's geometric mean query time was 690 ms at 1 TB and 5.6 seconds at 10 TB; a smaller Mega instance took 2 seconds at 1 TB. The 10 TB benchmark scans 168 TB across 99 queries. Comparisons use vendor or third-party results published in 2022, so they do not establish current speed rankings. MotherDuck ran unmodified DuckDB TPC-DS queries, reporting the best of three iterations per query and the geometric mean of hot query times. The author says some workloads still struggle to scale up and may need distributed support; DuckDB 2.0 improvements were not included.

### Source excerpt

The pursuit of all things duck-related has led us to some interesting places. In this blog, MotherDuck CEO Jordan Tigani explores the bigger, darker corners of benchmarks on top DuckDB 1.5 (and teases what is possible in DuckDB 2.0).

## Snowflake's Managed MCP Server: Giving AI Assistants a Governed Door Into Your Warehouse (Part 1)

DevFeed: [Snowflake's Managed MCP Server: Giving AI Assistants a Governed Door Into Your Warehouse (Part 1)](<https://devfeed.tech/articles/snowflake-s-managed-mcp-server-giving-ai-assistants-a-governed-door-into-your-warehouse-part-1-102727.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/snowflakes-managed-mcp-server-giving-ai-assistants-a-governed-door-into-your-warehouse-part-1-09077cd30c61?source=rss----34b6daafc07---4>)

Author: Eylon Steiner

Published: 2026-10-27T19:01:02Z

Content type: article

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [chat](<https://devfeed.tech/tags/chat.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [claude](<https://devfeed.tech/tags/claude.md>), [client](<https://devfeed.tech/tags/client.md>), [console](<https://devfeed.tech/tags/console.md>), [container](<https://devfeed.tech/tags/container.md>), [context](<https://devfeed.tech/tags/context.md>), [cortex](<https://devfeed.tech/tags/cortex.md>), [managed](<https://devfeed.tech/tags/managed.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [server](<https://devfeed.tech/tags/server.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [snowflake-data-superhero](<https://devfeed.tech/tags/snowflake-data-superhero.md>), [warehouse](<https://devfeed.tech/tags/warehouse.md>)

### AI overview

Snowflake's managed MCP server exposes warehouse tools as schema-level objects, with calls running under users' Snowflake identities and existing RBAC controls. The example separates a Cortex Agent backed by a semantic view and ticket search, plus a freshness procedure, from a second server with read-only SQL for engineers; placing SQL beside the agent could let a client bypass the semantic layer. The test found that generic procedures must return one cell (the author changed a table result to VARIANT), and unrestricted PATs combined with secondary roles could expose tools beyond the intended role. The author recommends role-restricted PATs and OAuth with secondary roles set to NONE. Query history records calls with the user, role and MCP request ID. Limits include tools only, 50 tools per server, 250 KB truncation for generic and SQL results, and manual OAuth client registration. The OAuth setup was not tested in the sandbox.

### Source excerpt

One door in, behind your own RBAC: that's the whole idea of the Snowflake-managed MCP server.This is Part 1 of a two-part series. Here I explain what MCP is, when you need Snowflake's managed MCP server, and build a full working example on Snowflake. In Part 2: Building a Chat UI for Snowflake's Managed MCP Server, I build a small web console that talks to the servers from this post.TL;DR MCP (Model Context Protocol) is a contract for tools. A client like Claude, Cursor or ChatGPT asks a server "what tools do you have?" (tools/list) and then calls them (tools/call). That's most of it. Snowflake can host the MCP server for you. It's a schema-level object (CREATE MCP SERVER) that exposes Cortex Agents, Cortex Analyst, Cortex Search, read-only SQL and your own UDFs and procedures as tools. You don't run a container, and access is just Snowflake RBAC. Expose an agent, not raw SQL. Snowflake's own recommendation, and mine after testing: one Cortex Agent tool for business users, and a separate server with read-only SQL for engineers. Watch secondary roles with PATs. In my test, a role with no grant on a server could still list its tools, because the PAT had no role restriction and the user had DEFAULT_SECONDARY_ROLES = ALL (the default). Give PATs a ROLE_RESTRICTION, and keep OAUTH_USE_SECONDARY_ROLES at its default of NONE on OAuth integrations. Custom procedure tools must return one cell. A RETURNS TABLE procedure fails over MCP. Return a VARIANT instead. Auditing is free. Every MCP call shows up in query history under the real user and role, tagged with the MCP request ID. Everything below ran in a sandbox account on Oct 8, 2026. The outputs are real. The Slack message that started this Every Monday our ops lead used to post the same thing in the data channel: "Are the dashboards up to date? And can someone pull revenue by region for last quarter?" Someone on the data team would check when the loads last ran, write a query, paste a screenshot, and answer three follow-u

## CVE-2026-116588 - Datadog dd-trace-py: ReDOS in URL query string obfuscation

DevFeed: [CVE-2026-116588 - Datadog dd-trace-py: ReDOS in URL query string obfuscation](<https://devfeed.tech/articles/cve-2026-116588-datadog-dd-trace-py-redos-in-url-query-string-obfuscation-100815.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-116588>)

Author: CVEFEED.io; github.com

Published: 2026-10-26T22:16:55Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Regular expression](<https://devfeed.tech/topics/regular-expression.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [datadog](<https://devfeed.tech/topics/datadog.md>)

Tags: [1-5](<https://devfeed.tech/tags/1-5.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [apm](<https://devfeed.tech/tags/apm.md>), [cause](<https://devfeed.tech/tags/cause.md>), [client](<https://devfeed.tech/tags/client.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-116588](<https://devfeed.tech/tags/cve-2026-116588.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [expression](<https://devfeed.tech/tags/expression.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [http](<https://devfeed.tech/tags/http.md>), [obfuscation](<https://devfeed.tech/tags/obfuscation.md>), [published](<https://devfeed.tech/tags/published.md>), [query](<https://devfeed.tech/tags/query.md>), [string](<https://devfeed.tech/tags/string.md>), [trace](<https://devfeed.tech/tags/trace.md>), [url](<https://devfeed.tech/tags/url.md>)

### AI overview

Datadog dd-trace-py versions from 1.5.0 up to (but not including) 3.19.9 and 4.15.6 are vulnerable to excessive backtracking in the default query-string obfuscation regex. In affected HTTP tracing integrations that include query strings in URL span tags, the regex processes attacker-controlled input synchronously and is enabled by default; a remote attacker can cause prolonged CPU use, request latency and service unavailability. The issue is fixed in versions 3.19.9 and 4.15.6.

### Source excerpt

CVE ID :CVE-2026-116588 Published : Oct. 26, 2026, 10:16 p.m. | 32 minutes ago Description :Datadog dd-trace-py is the Datadog Python APM client. From 1.5.0 until 3.19.9 and 4.15.6, the default query-string obfuscation regular expression can exhibit excessive backtracking while synchronously processing attacker-controlled URL query strings for HTTP span metadata. A remote attacker can cause prolonged CPU consumption, request latency, and service unavailability in affected HTTP tracing integrations that include query strings in URL span tags. The vulnerable processing is enabled by default for those integrations. This issue is fixed in versions 3.19.9 and 4.15.6. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## PostgreSQL Like A Pro: Build, query, and troubleshoot without leaving VS Code

DevFeed: [PostgreSQL Like A Pro: Build, query, and troubleshoot without leaving VS Code](<https://devfeed.tech/articles/postgresql-like-a-pro-build-query-and-troubleshoot-without-leaving-vs-code-100852.md>)

Original publisher: [Read original article](<https://devblogs.microsoft.com/blog/postgresql-like-a-pro-vscode/>)

Author: Cynthia Zanoni, Pooja Yarabothu

Published: 2026-10-26T15:05:12Z

Content type: tutorial

Language: en

Sources: [Developer Blogs](<https://devfeed.tech/sources/developer-blogs.md>)

Topics: [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>), [AI for SQL query generation](<https://devfeed.tech/topics/ai-for-sql-query-generation.md>)

Tags: [azure](<https://devfeed.tech/tags/azure.md>), [build](<https://devfeed.tech/tags/build.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [database](<https://devfeed.tech/tags/database.md>), [entra-id](<https://devfeed.tech/tags/entra-id.md>), [extension](<https://devfeed.tech/tags/extension.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [microsoft-for-developers](<https://devfeed.tech/tags/microsoft-for-developers.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [query](<https://devfeed.tech/tags/query.md>), [troubleshoot](<https://devfeed.tech/tags/troubleshoot.md>), [visual-studio-code](<https://devfeed.tech/tags/visual-studio-code.md>), [vs-code](<https://devfeed.tech/tags/vs-code.md>)

### AI overview

The PostgreSQL extension for VS Code brings database browsing, SQL editing, and Copilot-assisted work into the editor. Connect to on-premises or cloud databases, save reusable profiles, and browse schemas and objects; Azure connections can use Microsoft Entra ID. IntelliSense assists with SQL syntax and database names, while Copilot can help refine queries or interpret plans. The article advises reviewing generated SQL, execution plans, and results before adopting changes. For unfamiliar databases, use Object Explorer and schema visualization, then verify Copilot's database-context answers with the object tree and a read-only query. For performance issues, Database Agent in the Azure PostgreSQL experience is presented as an upcoming feature that assembles evidence and recommendations; actions are manual, availability and Azure requirements may apply, and automated remediation is described as future capability.

### Source excerpt

Build, query, and troubleshoot without leaving VS Code. The post PostgreSQL Like A Pro: Build, query, and troubleshoot without leaving VS Code appeared first on Microsoft for Developers.

[Next page](<https://devfeed.tech/topics/query.md?cursor=WyIyMDI2LTEwLTI2VDE1OjA1OjEyKzAwOjAwIiwgIjcxMDI0ODEzLTY0NmUtNGNkNC04MDFlLTMyOGNkNzUzM2JiZSJd>)