SeaQL / SeaQL/sea-orm

Allow the use of SmartString for strings

Open
#2,338 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area:type-map Category:enhancement
Dominant language
Rust
Stars
9.9k
Forks
734
Avg merge
6h 36m
Merged PRs (30d)
8

Description

In databases there are a lot of textual codes, most of which are short.

Using smartstring (or equivalent) may result in performance improvement, although I have not benchmarked it.

The idea being that of avoiding allocations for short strings, which should be the majority of text in a database.

Is there a way to override the default mapping for string data types to SmartString?

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

The issue names no files, tests, or entry points. First determine how SeaORM maps database string types and whether that mapping can be overridden with SmartString or an equivalent; the work is done when the supported approach and its performance impact are established.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
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.