search

logseq / db-test

Used for Database version test
6 stars 1 forks source link

Previous journal pages and their blocks should have create-at timestamp for their journal date #77

Open babygaogao opened 1 month ago

babygaogao commented 1 month ago

Search first

What Happened?

The inability to import past diaries is an important issue. Logseq's database version cannot import old logs by time, making data management difficult and hindering the handling of previous tasks and content.

Reproduce the Bug

Additionally, it is not possible to manually create logs with past dates, nor can users modify the creation dates in the database. There should at least be an option to allow users to modify the creation date of diary pages or to enable the import of old diaries, with timestamps automatically recorded based on the log page name, without needing to specify minutes and seconds.

image

logseq-cldwalker commented 3 weeks ago

Hi. Sorry for the delay

The inability to import past diaries is an important issue. Logseq's database version cannot import old logs by time

It's unclear what issue you're encountering as journals are importing as shown by your screenshot. Is the issue that the journal's created-at is wrong for some journals e.g. 2020/03/30 journal should have a 2020/03/30 created-at?

to enable the import of old diaries, with timestamps automatically recorded based on the log page name, without needing to specify minutes and seconds.

We could have a journal's created-at match the journal date if there is content in the journal. If there isn't content in the journal then that would be incorrect as the journal was created when it was referenced. Since previously Logseq didn't capture when a file was referenced it would need to be set to the current import time

logseq-cldwalker commented 2 weeks ago

Closing because of lack of response. Feel free to reopen with answers

babygaogao commented 1 week ago

Hi. Sorry for the delay

The inability to import past diaries is an important issue. Logseq's database version cannot import old logs by time

It's unclear what issue you're encountering as journals are importing as shown by your screenshot. Is the issue that the journal's created-at is wrong for some journals e.g. 2020/03/30 journal should have a 2020/03/30 created-at?

to enable the import of old diaries, with timestamps automatically recorded based on the log page name, without needing to specify minutes and seconds.

We could have a journal's created-at match the journal date if there is content in the journal. If there isn't content in the journal then that would be incorrect as the journal was created when it was referenced. Since previously Logseq didn't capture when a file was referenced it would need to be set to the current import time

hi，We need to import old Logseq data, and many previous diaries have recorded a lot of blocks. Ideally, both the diary page from 2021/03/31 and the timestamps of the blocks on that page should have a creation date of 2021/03/31, instead of being marked with the timestamp of when the new database version is imported. The current issue with Logseq's database is that it recognises all the imported past data as being created on the day it was imported, which makes it hard to manage old data. Plus, there are still so many other mates who need to migrate their data. We hope this issue can be fixed because even manually going through each diary to address this problem isn’t feasible. We need your help, thanks!