We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Parser.clear() does not clear anything until session.commit() is executed elsewhere. According to https://docs.sqlalchemy.org/en/13/orm/session_basics.html#deleting,
Parser.clear()
session.commit()
The Session.delete() method places an instance into the Session’s list of objects to be marked as deleted
Steps to reproduce the behavior:
>>> corpus_parser.apply(doc_preprocessor) >>> corpus_parser.clear() >>> assert session.query(Document).count() == 0
When corpus_parser.clear() above is executed, any instance of Context like Document, Sentence should be deleted.
corpus_parser.clear()
Context
Document
Sentence
If applicable, add error logs or screenshots to help explain your problem.
Add any other context about the problem here.
This might be related to #213
The text was updated successfully, but these errors were encountered:
I'm trying to write a unit test that can reproduce this issue, but can't. Close for now.
Sorry, something went wrong.
No branches or pull requests
Description of the bug
Parser.clear()
does not clear anything untilsession.commit()
is executed elsewhere.According to https://docs.sqlalchemy.org/en/13/orm/session_basics.html#deleting,
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When
corpus_parser.clear()
above is executed, any instance ofContext
likeDocument
,Sentence
should be deleted.Error Logs/Screenshots
If applicable, add error logs or screenshots to help explain your problem.
Environment (please complete the following information)
Additional context
Add any other context about the problem here.
This might be related to #213
The text was updated successfully, but these errors were encountered: