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

Bookmarks with dates #745

Open
pycaw opened this issue Jun 12, 2024 · 3 comments
Open

Bookmarks with dates #745

pycaw opened this issue Jun 12, 2024 · 3 comments

Comments

@pycaw
Copy link

pycaw commented Jun 12, 2024

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

@LeXofLeviafan
Copy link
Collaborator

LeXofLeviafan commented Jun 12, 2024

I've been thinking of extending bookmark records with custom fields (previously mentioned here and here) which might potentially include date/datetime fields, but I don't have a timeline on that.

@sjehuda
Copy link
Contributor

sjehuda commented Jul 14, 2024

I've been thinking of extending bookmark records with custom fields

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?

@LeXofLeviafan
Copy link
Collaborator

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.)

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

No branches or pull requests

3 participants