PostgreSQL sorts and compares text by the database collation, unlike the other providers

Open
#3,308 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, postgresql
Domain
database

Research direction

Start with src/FluentCMS.Data.PostgreSql/PostgreSqlStorageConventions.cs and compare its text-column configuration with src/FluentCMS.Data.SqlServer/SqlServerStorageConventions.cs; then read the base method in src/FluentCMS.Core/Storage/StorageConventions.cs. Locate the specification around lines 524–527, provider tests, content migration patterns, and release notes. Done means text sorting and range filters agree across providers, existing PostgreSQL content tables are migrated, and a regression test fails before the fix.

Written by the indexing model from the issue text.

Description

area:storage type:bug

Problem

src/FluentCMS.Data.PostgreSql/PostgreSqlStorageConventions.cs does not override ConfigureTextColumn (the base is a no-op, src/FluentCMS.Core/Storage/StorageConventions.cs:28). SQL Server sets a binary collation (src/FluentCMS.Data.SqlServer/SqlServerStorageConventions.cs:31, from #2874) and SQLite compares bytes. On PostgreSQL, sort order and lt/gt on text follow the database collation, so the same query returns a different order or a different set than on the other providers.

Proposal

Use the C collation on content text columns in PostgreSQL, with a content migration for existing tables. Add the line to the specification next to the SQL Server one (lines 524–527). The release notes must say that sort order changes for existing PostgreSQL data.

Acceptance

  • Sort and range filters on text return the same result on all three providers
  • Existing content tables are altered by a migration
  • A provider test that fails before the fix

Found in the code review of 17 Nov 2026.

Dominant language
C#
Stars
569
Forks
107
Avg merge
2h 49m
Merged PRs (30d)
397

Getting set up

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.

More from fluentcms/FluentCMS

All issues in fluentcms/FluentCMS

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.