1c-query-opt

Optimize slow 1C:Enterprise queries by restructuring JOINs, virtual table filters, and result composition.

151|20|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill 1c-query-opt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-query-opt
Source: https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/main/.claude/skills/1c-query-opt
Command: npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill 1c-query-opt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps resolve slow or inefficient 1C:Enterprise query performance by guiding you toward query patterns that better fit the platform’s execution model.

Core Features & Use Cases

  • Optimizes JOIN and subqueries: recommends using JOIN correctly, avoiding N+1 patterns, and replacing problematic joins with temporary tables.
  • Improves virtual table usage: encourages pushing filters into virtual table parameters and preventing unnecessary post-filtering.
  • Stabilizes query shape for the optimizer: suggests expressing composite types, using presentation for display, combining OR conditions carefully, and choosing between ОБЪЕДИНИТЬ and ОБЪЕДИНИТЬ ВСЕ appropriately.
  • Guides temporary-table workflows and indexing: advises extracting to temporary tables first, then joining, with correct INDX/IINDEXATION strategies.

Quick Start

Ask the AI to optimize your slow 1C query by applying temporary tables, correct virtual table filtering, and safe index/UNION patterns without changing the intended business result.

Frequently Asked Questions about 1c-query-opt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize slow 1C:Enterprise queries for large datasets?

To optimize slow 1C:Enterprise queries, restructure JOIN and subquery patterns, push filters directly into virtual table parameters using ИЗ ... ПАРАМЕТРЫ, and extract intermediate results into temporary tables with proper indexing.

Why does my 1C virtual table query perform poorly during report generation?

1C virtual table queries perform poorly when filters are applied after data retrieval instead of being pushed into virtual table parameters, causing the platform to process unnecessary post-filtering on large datasets.

When should I use temporary tables instead of subqueries in 1C?

Use temporary tables instead of complex subqueries in 1C when you need to stabilize the query shape for the optimizer, applying INDX and INNDXATION strategies to improve multi-step data processing performance.

What is the difference between ОБЪЕДИНИТЬ and ОБЪЕДИНИТЬ ВСЕ when tuning СКД queries?

ОБЪЕДИНИТЬ removes duplicate rows while ОБЪЕДИНИТЬ ВСЕ retains all rows, and choosing the correct UNION strategy carefully stabilizes the query shape and prevents inefficient execution during СКД report tuning.

How do I handle composite types safely in 1C query optimization?

Handle composite types safely in 1C query optimization by explicitly expressing them in the query structure and using presentation for display, which stabilizes the query shape for the platform's execution model.

Can I fix N+1 query patterns in 1C without changing the business result?

You can fix N+1 query patterns by replacing problematic joins with temporary tables and restructuring JOIN usage to better fit the 1C:Enterprise execution model without altering the intended business result.