<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ydb/yql/essentials/sql/v1/sql_ut_common.h, branch meta-1.0.3</title>
<subtitle>Mirror of YDB github repos</subtitle>
<id>https://code.mastervirt.ru/ydb/atom?h=meta-1.0.3</id>
<link rel='self' href='https://code.mastervirt.ru/ydb/atom?h=meta-1.0.3'/>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/'/>
<updated>2025-07-21T14:07:14Z</updated>
<entry>
<title>New ASYNC REPLICATION's option: CA_CERT</title>
<updated>2025-07-21T14:07:14Z</updated>
<author>
<name>ilnaz</name>
<email>ilnaz@yandex-team.com</email>
</author>
<published>2025-07-21T13:10:13Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=bd13b1b03f862c3fb50c30c35cd976376c9d63ae'/>
<id>urn:sha1:bd13b1b03f862c3fb50c30c35cd976376c9d63ae</id>
<content type='text'>
commit_hash:ce61d0c6dad2e170eface04d63918adc1082e56e
</content>
</entry>
<entry>
<title>Feature: alter table T alter column C set not null</title>
<updated>2025-07-21T12:11:34Z</updated>
<author>
<name>flown4qqqq</name>
<email>flown4qqqq@yandex-team.com</email>
</author>
<published>2025-07-21T11:57:17Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=646c5b82467945d8cdfc5d5f716ae2acb30a8313'/>
<id>urn:sha1:646c5b82467945d8cdfc5d5f716ae2acb30a8313</id>
<content type='text'>
Когда-то давно (когда еще YQL жил в github) была поставлена задача - поддержать SET/DROP NOT NULL на колонку. DROP NOT NULL был сделан и давно уже существует в main: &lt;https://github.com/ydb-platform/ydb/pull/6342&gt;.

Однако с SET NOT NULL возникли определенные сложности, поэтому был сделан отдельный пулл реквест: &lt;https://github.com/ydb-platform/ydb/pull/6341&gt;. Как видно, ПР так и не вмержили по причине увольнения автора кода. Недавно задача всплыла вновь, поэтому надо доделать.

В этом пулл реквесте добавляется код в грамматику YQL новое выражение - `ALTER TABLE t ALTER COLUMN c SET NOT NULL`, которая добавляет ограничение `NOT NULL` на колонку.
commit_hash:f310061b13666418c46309ea32032fbce68fb865
</content>
</entry>
<entry>
<title>YQL-20171: Fix aggregation joining key</title>
<updated>2025-07-15T14:19:51Z</updated>
<author>
<name>vitya-smirnov</name>
<email>vitya-smirnov@yandex-team.com</email>
</author>
<published>2025-07-15T14:01:51Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=64137fb0cbe9afe92dca8efc335ef9ff16b78926'/>
<id>urn:sha1:64137fb0cbe9afe92dca8efc335ef9ff16b78926</id>
<content type='text'>
There was a bug with a aggregation deduplication
by a column at the translator.

For a single column the system joining all
aggregations using the generic key. The
generic key was just a column name without
source name what leads to collision when
aggregating multiple different sources with
same column names.

This patch fixes the generic key by adding a
data source name there. Also tests are added.
commit_hash:1c0a9da512f68c58d2830e096de76b769b733cb2
</content>
</entry>
<entry>
<title>YQL-17269: Support UNION/INTERSECT/EXCEPT combinations</title>
<updated>2025-07-09T11:38:43Z</updated>
<author>
<name>vitya-smirnov</name>
<email>vitya-smirnov@yandex-team.com</email>
</author>
<published>2025-07-09T11:16:01Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=59c3167c208900bb714ff5cc477476e3ab14f4f0'/>
<id>urn:sha1:59c3167c208900bb714ff5cc477476e3ab14f4f0</id>
<content type='text'>
Introduce `UNION` and `INTERSECT/EXCEPT` grammar rules
for precedence. Rewrote `Build` procedure into `BuildStmt`,
`BuildUnion`, `BuildIntersection`. Added tests, modify format.

It took a lot of time trying to adapt the existing `Build` procedure.
The I noticed that the logic for `union` and `intersection` is
different, since `union` groups arguments into bundles, but
`intersection` is a strictly binary operation.
commit_hash:70008ae3c2603364b6dfbeeb189fdc7f5237433d
</content>
</entry>
<entry>
<title>YQL-17269: restrict multiple INTERSECT and EXCEPT</title>
<updated>2025-06-30T12:05:46Z</updated>
<author>
<name>kndrvt</name>
<email>kndrvt@yandex-team.com</email>
</author>
<published>2025-06-30T11:40:06Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=118cd9ce9b40173fc06e327961e4d38d2dc727a8'/>
<id>urn:sha1:118cd9ce9b40173fc06e327961e4d38d2dc727a8</id>
<content type='text'>
commit_hash:635c8def3bba6890d2d80b418fca9bec6cbd4b73
</content>
</entry>
<entry>
<title>YQL-17269: support PositionalUnionAll for INTERSECT and EXCEPT</title>
<updated>2025-06-23T17:14:16Z</updated>
<author>
<name>kndrvt</name>
<email>kndrvt@yandex-team.com</email>
</author>
<published>2025-06-23T16:28:22Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=db2354704a30f375d445bfc3aea9eac5975562af'/>
<id>urn:sha1:db2354704a30f375d445bfc3aea9eac5975562af</id>
<content type='text'>
commit_hash:4c68311d9e875b6643dd49aae1c385aace4ca978
</content>
</entry>
<entry>
<title>YQL-17269: support INTERSECT and EXCEPT without PositionalUnionAll</title>
<updated>2025-06-20T13:07:13Z</updated>
<author>
<name>kndrvt</name>
<email>kndrvt@yandex-team.com</email>
</author>
<published>2025-06-20T12:36:52Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=935e53d2a9ee4b43cc0548ba836b23c003c8078e'/>
<id>urn:sha1:935e53d2a9ee4b43cc0548ba836b23c003c8078e</id>
<content type='text'>
commit_hash:632e24794e8bcf6ef0502b7e8c031e964d28d36a
</content>
</entry>
<entry>
<title>support database settings in ALTER DATABASE</title>
<updated>2025-06-04T09:51:33Z</updated>
<author>
<name>deminds</name>
<email>deminds@yandex-team.com</email>
</author>
<published>2025-06-04T09:36:47Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=14c42c6f9a85a081cde9ba58db0b008b3ade11f7'/>
<id>urn:sha1:14c42c6f9a85a081cde9ba58db0b008b3ade11f7</id>
<content type='text'>
The main goal is to enable setting SchemeLimits (ShardsLimit and PathsLimit) via YQL.

Issue:
- https://github.com/ydb-platform/ydb/issues/16742
commit_hash:e873849e3b4bb494e349ccebbb1ff6d51655c5d1
</content>
</entry>
<entry>
<title>New CHANGEFEED's option: SCHEMA_CHANGES</title>
<updated>2025-06-03T09:51:48Z</updated>
<author>
<name>ilnaz</name>
<email>ilnaz@yandex-team.com</email>
</author>
<published>2025-06-03T09:11:48Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=3e8add594e2ff4cf7ff8f552e9a6e285f4d6c372'/>
<id>urn:sha1:3e8add594e2ff4cf7ff8f552e9a6e285f4d6c372</id>
<content type='text'>
commit_hash:23ba332ac8979f2e4e62231fb47414233ee4043e
</content>
</entry>
<entry>
<title>YQL-17269: add DISTINCT to UNION</title>
<updated>2025-05-27T09:35:09Z</updated>
<author>
<name>kndrvt</name>
<email>kndrvt@yandex-team.com</email>
</author>
<published>2025-05-27T09:21:32Z</published>
<link rel='alternate' type='text/html' href='https://code.mastervirt.ru/ydb/commit/?id=66037646e2c2d277e0406a6b23eca63b62357916'/>
<id>urn:sha1:66037646e2c2d277e0406a6b23eca63b62357916</id>
<content type='text'>
commit_hash:d002e9690bd7cbd1874fdbfe454c9f7a00256839
</content>
</entry>
</feed>
