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.

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

ISSUES - NEW ISSUE - POSTING - LOST points across ISSUES #3656

DingBEN opened this issue Feb 2, 2020 · 0 comments

ISSUES - NEW ISSUE - POSTING - LOST points across ISSUES #3656

DingBEN opened this issue Feb 2, 2020 · 0 comments


Copy link

@DingBEN DingBEN commented Feb 2, 2020



  • When one is trying to do work with an app in conjunction with evaluating it and encounters so many issues in the process, it is hard to CREATE separate POSTS/ISSUES for each singled out entry.
  • ...first, it is not always clear that an underlying issue exists or which
  • one may not think right away of the separate entity that indeed belongs
  • many separate issues are resolved by one sweeping move, [ ex: colors in config ]

I have edited the existing issues and inserted after-thoughts or new findings that belong in a particular issue.
flagged as follows ->: UPDATE: yy-mm-dd hh:mn

  • I also store each issue in a table of issues with title and full text, so I can apply SQL searches which return rowid, title and appended text.
  • One could take all my posts and append them into a text file and arrive at a comparable search power

anyhow, that should now taper off, thus I will create new entries, rather than update, unless an UPDATE makes better sense, while applying the thinking that an UPDATE is not a good idea... for the obvious reasons. I have no idea how this POSTING SYSTEM flags edits, thus keep in mind that UPDATEs may be buried in the wheat.
Hopefully there is a way to single out all the posts of a single person.

Operating system - WIN7 Pro

SQLiteStudio version - 3.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.