Skip to content

Record 15 bugs from a full sweep of main in BUGS.md - #11

Open
robertsolves wants to merge 1 commit into
mainfrom
claude/project-thread-l4bx1s
Open

robertsolves wants to merge 1 commit into
mainfrom
claude/project-thread-l4bx1s

Conversation

@robertsolves

Copy link
Copy Markdown
Collaborator

Requested by Robert · project thread

What & why

A full bug sweep of main at 195d46b. This PR only changes BUGS.md: it adds 15 entries, ordered most harmful first. No code changes. The fixes can follow in their own PRs.

The worst ones:

  • Editing a numeric cell rounds it through a double, so the wrong number gets saved (data loss).
  • Editing interval and time cells always errors. Editing bytea cells always reports a conflict.
  • money, inet, macaddr, timetz and bit columns show as hex or garbage, and can't be edited.
  • On the web proxy, any JSON object value fails the whole query (entry.key.toString is a tear-off), and every column type reads Type(oid:N).
  • Copy table fails on tables with generated columns.
  • Tables without a primary key silently show only 500 rows.
  • The shell env file ignores source ~/... and reads backslashes wrong.

How it was tested

fvm flutter analyze is clean and fvm flutter test passes (322 tests) on Linux. Most entries were confirmed with throwaway probe tests against Postgres 16 and SQLite in the container. The probes are not committed. Each entry says whether it was confirmed or inferred from reading the code.

Checklist

  • fvm flutter analyze is clean
  • fvm flutter test passes
  • SQL safety invariants still hold (no code changed)
  • No credentials, API keys or .dbscopeconn files in the diff

Generated by Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EqzDdWi2HDSEsrAhdHHxmj

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants