Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C csvkit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wireservice
  • csvkit
  • Issues
  • #21
Closed
Open
Issue created Apr 12, 2011 by Administrator@rootContributor

Try/except block in outer joins isn't atomic

Created by: JoeGermuska

I'm sketched out by the append-in-for-loops inside a try-catch block.

It doesn't look atomic to me. What if there were an exception midway-through adding a row? come columns which already had a value would have a None also appended, no?

I don't have time to write a test case tonight, so maybe I'm missing something or maybe there's a test for it already and you should just tell me to RTFC.

anyway, it might be nice to abstract an _outer_join method. I was starting down that path, passing in keys and some rules about when to allow for None values. I'm reading this code trying to decide how to handle the one-to-many case.

Assignee
Assign to
Time tracking