TryGhost/Ghost

Cannot get posts from the same date (SQLite3-specific?)

Open

#23,441 opened on May 20, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (11,551 forks)batch import
affects:apibugcommunitygood first issue

Repository metrics

Stars
 (52,799 stars)
PR merge metrics
 (Avg merge 19d 11h) (658 merged PRs in 30d)

Description

Issue Summary

In sqlite3, dates are formatted in the published_at column of the posts table as '2025-04-22 14:13:46'. (Note the space, lack of T, etc.) Using {{published_at}} in the theme gives you something like: 2025-04-22T10:13:46.000-04:00 So let's say I want posts newer and older than my current page's publication date.

Posts before: 2025-02-27T19:03:00.000-05:00 2025-02-13T19:02:00-05:00 2025-02-13T19:02:00-05:00 2025-02-13T19:02:00-05:00 2025-02-13T19:02:00-05:00 2025-02-13T19:02:00-05:00 2025-01-23T19:01:00-05:00 2025-01-23T19:01:00-05:00 2025-01-23T19:01:00-05:00 I'm getting the posts published at 2025-02-13T19:02:00-05:00 showing up as being after 2025-02-27T19:02:00-05:00 My guess here is that the filter is using the format the posts are in from the database. But there's no T in that date format, so everything from that date is after the published_at, because T > " "

Steps to Reproduce

see above

Ghost Version

5.116

Node.js Version

20

How did you install Ghost?

local install

Database type

SQLite3

Browser & OS version

No response

Relevant log / error output

Code of Conduct

  • I agree to be friendly and polite to people in this repository

Contributor guide

Research direction
Investigate how Ghost's filter system compares dates. The issue likely stems from SQLite storing dates with a space instead of 'T', causing string comparison to fail. Check the implementation of the filter parser or database adapter to ensure dates are normalized to ISO 8601 before comparison.
Tech stack
javascriptnodejssqlite
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70