Skip to content

should truncate() do delete() instead of drop() ? #85

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
Closed
bitinn opened this issue Dec 10, 2013 · 0 comments
Closed

should truncate() do delete() instead of drop() ? #85

bitinn opened this issue Dec 10, 2013 · 0 comments

Comments

@bitinn
Copy link

bitinn commented Dec 10, 2013

using drop() will also remove indexes, i were kinda expecting it to just remove all rows. We already have schema for dropping collection right?
@GromNaN GromNaN mentioned this issue Aug 21, 2024
Merged
3 tasks
mnphpexpert added a commit to mnphpexpert/laravel-mongodb that referenced this issue Sep 2, 2024
@mnphpexpert
Use remove for truncate, fixes mongodb#85
832f321
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bitinn