psibi/odbc-issue-49 — explained in plain English
Analysis updated 2026-07-11 · repo last pushed 2022-04-26
Reproduce an ODBC character encoding bug to accompany a bug report.
Debug a similar Unicode encoding mismatch in your own Haskell ODBC setup.
Compare how different database column types return special characters through ODBC.
| psibi/odbc-issue-49 | bobymicroby/boby-alga-toolkit | psibi/mime-mail | |
|---|---|---|---|
| Stars | 1 | — | — |
| Language | Haskell | Haskell | Haskell |
| Last pushed | 2022-04-26 | 2021-02-10 | 2018-04-18 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | moderate | easy | easy |
| Complexity | 1/5 | 2/5 | 2/5 |
| Audience | developer | pm founder | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a configured ODBC data source and a database with specific test columns containing Unicode characters.
This repository is a minimal test case demonstrating a specific character encoding issue with ODBC database connections in Haskell. It exists to reproduce and illustrate a problem rather than serve as a tool you'd install and use. ODBC is a standard way for programs to talk to databases like SQL Server or PostgreSQL. When a Haskell program connects to a database through ODBC and retrieves text, there's a question of how characters are represented. This repo shows that the pound sign (£) comes back in two different forms depending on the column type: as a proper text character or as a raw byte sequence. The output in the README demonstrates this discrepancy side by side. The intended audience is likely the maintainer of a Haskell ODBC library or someone debugging a similar encoding mismatch. When a database stores Unicode characters like the pound sign, different column types may return data differently through ODBC, and this repo isolates that behavior so it can be discussed or fixed. It's the kind of project you'd create to accompany a bug report, small, focused, and showing exactly what happens when you run it. There's no real documentation beyond the terminal output itself, so you'd need to look at the Haskell source to understand which database it connects to and how the test table is set up. The project is built with Stack, which is a common Haskell build tool, but the README doesn't walk through setup steps or explain the broader context of the issue.
A minimal Haskell test case that reproduces a character encoding bug with ODBC database connections, showing how the pound sign (£) is returned differently depending on column type.
Mainly Haskell. The stack also includes Haskell, Stack, ODBC.
Dormant — no commits in 2+ years (last push 2022-04-26).
No license information is provided in this repository.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.