<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirserver/src/schema_v1.sql, branch main</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=main</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-04-28T16:27:44Z</updated>
<entry>
<title>tor-dirserver: Make fingerprint optional in router_descriptor</title>
<updated>2026-04-28T16:27:44Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-04-23T15:30:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=86f129e1ae01cac52912d3fbb1a0fef320d52ce7'/>
<id>urn:sha1:86f129e1ae01cac52912d3fbb1a0fef320d52ce7</id>
<content type='text'>
This commit changes the schema to make the fingerprint optional.
Reason for this is, that microdescriptors are also stored in this table
and microdescriptors only contain an OPTIONAL onion-key, meaning it may
not always be possible to determine this value from a microdescriptor,
thereby making it silly to require it here.
</content>
</entry>
<entry>
<title>tor-dirserver: Store precisely one descriptor hash in schema</title>
<updated>2026-04-27T15:46:58Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-04-14T08:49:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0b07bd3ee6a19af1025c02c52971a9071b937620'/>
<id>urn:sha1:0b07bd3ee6a19af1025c02c52971a9071b937620</id>
<content type='text'>
This commit modifies the consensus_router_descriptor_member table in the
database schema, removing the NOT NULL constraint on unsigned_sha1 and
unsigned_sha2 by replacing it with a new CHECK constraint that checks
that either one of them is set but not both.

The reason for this is as follows: We are going to use this table to
compute the queue of missing descriptors, which means that we can only
populate this table with the data we know from the consensus.  The
consensus however tells us only one of those hashes, namely sha1 in the
case of a consensus-ns and sha2 in the case of a consensus-md.

In other words: This commit can also be seen as an effort to change the
design of the operation in such a way that the queue is obtained
directly from the database and not computed at the start during state
transition.
</content>
</entry>
<entry>
<title>Fix typos</title>
<updated>2026-03-24T16:04:08Z</updated>
<author>
<name>Tobias Stoeckmann</name>
<email>tobias@stoeckmann.org</email>
</author>
<published>2026-03-24T16:04:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1fb2b8dd4aee7c943ce90d6631be473f2a296fe6'/>
<id>urn:sha1:1fb2b8dd4aee7c943ce90d6631be473f2a296fe6</id>
<content type='text'>
Typos found with codespell
</content>
</entry>
<entry>
<title>tor-dirserver: SQL comment for unsigned hashes</title>
<updated>2026-03-09T08:31:28Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-03-02T14:03:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b9769c61e7b9d8c16cf07dde74141c475f37e639'/>
<id>urn:sha1:b9769c61e7b9d8c16cf07dde74141c475f37e639</id>
<content type='text'>
This commit documents why and how we use the `unsigned_` fields in the
`consensus_router_descriptor_member` table alongside SQL limitations.
</content>
</entry>
<entry>
<title>tor-dirserver: Remove fiddly SQL CHECK</title>
<updated>2026-03-09T08:31:28Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-02-25T11:10:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=71aaf644bc746f45c40e98db86a2e60bbdb5ed54'/>
<id>urn:sha1:71aaf644bc746f45c40e98db86a2e60bbdb5ed54</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-dirserver: Move schema to own file</title>
<updated>2026-03-09T08:31:28Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-02-25T09:11:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7814e15ae0f88da389349d2ada0e1101f235063c'/>
<id>urn:sha1:7814e15ae0f88da389349d2ada0e1101f235063c</id>
<content type='text'>
This commit moves the database schema into schema_v1.sql and uses
include_str to include it.  For now, the schema lives in the `src/`
directory.  If this becomes a problem because we get more schemas and
schema upgrades, we can move it into another sub directory, but let's
not overengineer the hierarchy there.
</content>
</entry>
</feed>
