• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

go-sql-driver / mysql / 25624538760 / 1
83%
master: 83%

Build:
Build:
LAST BUILD BRANCH: fix/ParseDSN-colon-in-username
DEFAULT BRANCH: master
Ran 10 May 2026 01:47PM UTC
Files 18
Run time 7s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

10 May 2026 08:53AM UTC coverage: 81.769% (-0.1%) from 81.892%
25624538760.1

Pull #1768

github

Nghĩa Nguyễn Ngọc
dsn: document that usernames with colons require NewConfig()

The DSN format uses ':' as the user/password separator, making it
impossible to represent a username that contains a colon without
ambiguity. There is no safe way to fix this in ParseDSN without
breaking existing users who rely on the current first-colon behaviour
for passwords that contain colons.

Instead, document the limitation clearly in the ParseDSN godoc and
point callers to NewConfig(), which has no such ambiguity.

Fixes #1747
Pull Request #1768: dsn: document that usernames containing colons require NewConfig()

3319 of 4059 relevant lines covered (81.77%)

83756.94 hits per line

Source Files on job Windows-Go-1.26-DB-8.4 - 25624538760.1
  • Tree
  • List 18
  • Changed 4
  • Source Changed 0
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 25624538760
  • 4825420a on github
  • Prev Job for on fix/ParseDSN-colon-in-username (#25111743223.14)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc