logseq / logseq/db-test

Some pages have wrong creation and update date after import

Open
#1,047 7 comments 0 reactions 1 assignee View on GitHub

@megayu is already working on this.

Since Aug 17, 2026.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I now checked your implementation of using the actual page creation date instead of the import date. I found 2 issues.

The import date is still used for 3/4 of my imported pages. Those are pages that have no content, so no file for them exist or have only aliases defines.

In both cases, you are able to estimate the creation time. For pages with alias, there is a file which creation and modify date you can use. For pages that exist only because they are linked in the journal, use the date from the journal where it was first mentioned.

### Reproduce the Bug

1. Import OG Graph
2. Check dates of Pages

### Expected Behavior

Correct data after import

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

NixOS 26.05.4659.8f0500b96605
Logseq-linux-x86_64-2.0.1-alpha+nightly.20260728

### Additional Context

This is again a situation that does not give me confidence in the quality of your work. You should have tested this and found this issues before merging!

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.