sqlite: DELETE FROM does not work
Describe the bug
I cannot longer DELETE FROM. Am I required to add a sql_deleted now? This does not match our design/model and we have no upstream database to sync with. Can we have the old behaviour back or at least add an option like “strict” mode or something like that. We really need to remove everything not update a table col.
To Reproduce Steps to reproduce the behavior:
- Go to ‘…’
- Click on ‘…’
- Scroll down to ‘…’
- See error
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Smartphone (please complete the following information):
- Device: [e.g. iPhone6] iPhone 13 Pro
- OS: [e.g. iOS8.1] latest
- Browser [e.g. stock browser, safari]
- Version [e.g. 22] latest
Additional context Add any other context about the problem here.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 34 (13 by maintainers)
Commits related to this issue
- Fix #271 for iOS & added support for table name containing character dash/hyphen (-) — committed to victorybiz/sqlite by victorybiz 2 years ago
- Merge pull request #291 from victorybiz/master Fix #271 for iOS & added support for table name containing dash/hyphen — committed to capacitor-community/sqlite by jepiqueau 2 years ago
- fix issue#283 & #271 — committed to capacitor-community/sqlite by jepiqueau 2 years ago
My issue continues to occur. You can reproduce it here: https://github.com/muuvmuuv/issue-capacitor-sqlite/commit/9d0e472c148c300b394435de06ff348907c0a0bc
It did fix it though by adding the semicolon at the end of the delete statement. I guess the newer version is somehow “stricter” in syntax.
@rengadevigg yes like every SQLite statement
@rengadevigg query is made for SELECT statement and not for DELETE statement for this you must use RUN or EXECUTE with à semi column at the end
@victorybiz this has been fixed in 3.5.1-1