Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

write.over doesn't replace; should use TRUNCATE_EXISTING #441

Closed
nafg opened this issue Aug 19, 2016 · 1 comment
Closed

write.over doesn't replace; should use TRUNCATE_EXISTING #441

nafg opened this issue Aug 19, 2016 · 1 comment
Labels
bug

Comments

@nafg
Copy link
Contributor

nafg commented Aug 19, 2016

No description provided.

@nafg nafg changed the title write.over doesn write.over doesn't replace; should use TRUNCATE_EXISTING Aug 19, 2016
@nafg nafg changed the title write.over doesn't replace; should use TRUNCATE_EXISTING write.over doesn't replace; should use TRUNCATE_EXISTING Aug 19, 2016
@lihaoyi lihaoyi added the bug label Aug 21, 2016
@lihaoyi
Copy link
Member

lihaoyi commented Aug 21, 2016

I have been bitten by this too!

lihaoyi pushed a commit that referenced this issue Aug 28, 2016
enable TRUNCATE_EXISTING to fix #441
bda045f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nafg @lihaoyi