-
-
Notifications
You must be signed in to change notification settings - Fork 294
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
Bookmarks with dates #745
Comments
How do you think could this be done with SQLite? Will buku create a new table (i.e. CREATE a new table and then DROP the old table) or would it be in another fashion? |
To have proper custom fields, they'll need to match bookmark records many-to-one, so a separate table would be needed. (And also at least one more to store settings – those being descriptions of said custom fields, at the very least.) Such changes should not break backward compatibility, at least for purpose of reading and updating existing records (and if SQL triggers work as expected in SQLite, then there would be no issues with data consistency either). Though of course any legacy clients (such as Bukubrow, which operates the DB file directly and had no updates for the last 2 years) would remain unaware of such fields, and would neither display nor update them. (…Technically in case of specifically record creation/modification dates it's possible to implement them as triggers, but I haven't had a chance to estimate feasibility nor demand for supporting that kind of a feature.) |
I tried boku years ago and the lack of ability to include dates (addition date) made me ditch it. Even though I loved the idea.
Can we not expect change in this regard? Does it really go against the design philosophy?
Apart from bookmark creation/addition date, modification date and update date (last check for aliveness) could also be useful.
Related & scrapped feature requests:
#588
#304
The text was updated successfully, but these errors were encountered: