typelevel / typelevel/skunk

Consider the use of binary format vs text in message protocol

Open
#837 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.7k
Forks
175
Avg merge
5d 14h
Merged PRs (30d)
9

Description

https://www.postgresql.org/docs/current/protocol-overview.html#PROTOCOL-FORMAT-CODES

Binary representations for integers use network byte order (most significant byte first). For other data types consult the documentation or source code to learn about the binary representation. Keep in mind that binary representations for complex data types might change across server versions; the text format is usually the more portable choice.

Perhaps start with the core data types? Even just start with int? Can you mix/match text/binary in the same request with some fields being binary and others text?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the PostgreSQL protocol format-codes documentation linked in the issue. Investigate how core data types, beginning with integers, are represented and whether one request can mix binary and text fields. The scope is complete when the supported formats and mixed-mode behavior are clearly decided and documented or implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres, scala
Domain
database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.