Date field

import { collection } from "#questpie/factories";

export const announcements = collection("announcements").fields(({ f }) => ({
	validFrom: f.date().required(), // date NOT NULL, string on read
	validTo: f.date(), // nullable
}));

The factory takes no config. Three methods change the column. .array() swaps it for jsonb, .drizzle() hands you the builder, and .localized() moves it to the i18n table.

The value is a string

Postgres holds a real date. Drizzle's string mode hands that text back untouched. So the field is a string in the row, in the insert and in the where. Ordering and ranges still run in the database, on a date column.

Methods

Two methods come with the type. .required(), .default(), .label(), .localized() and the rest of the base chain work here as on any field.

Both compute new Date().toISOString().slice(0, 10). Today means the UTC calendar day. It is never a tenant day or a business day.

collection("posts").fields(({ f }) => ({
	publishedOn: f.date().autoNow(),
	reviewedOn: f.date().autoNowUpdate(),
}));

Neither method changes the field's type. So f.date().required().autoNow() still demands the key in TypeScript. The runtime schema accepts the create without it, because hasDefault makes the input optional.

.autoNowUpdate() keeps the field's other hooks and replaces beforeChange. Call .hooks({}) before it, never after. A later .hooks({}) replaces the whole bag.

.inputFalse() denies create and update on the field, so sending the key is a 403. .autoNow() survives that. Its value comes from the column DEFAULT, not from your payload. .autoNowUpdate() does not survive it. The hook needs the key, and the key is now a 403. Put a value you want on every write in a collection beforeChange hook instead. That one runs either way.

Filtering

A date field carries the date-string operator set. The operator object in its where entry types to exactly these eleven keys.

A bare value is the shorthand and types alongside that object. { validFrom: "2026-08-01" } compiles to eq. { validTo: null } compiles to IS NULL.

const today = new Date().toISOString().slice(0, 10);
const { docs } = await app.collections.announcements.find({
	where: { validFrom: { lte: today }, validTo: { gte: today } },
});

Every operand is checked before it reaches SQL. The nine value operators run through an exact calendar-date parse. Anything but a YYYY-MM-DD string is a 400 reading Date filters require an exact YYYY-MM-DD calendar date. isNull, isNotNull and not: null skip that check. The SQL is the comparison f.datetime() builds. Only the operand type differs.

In the admin

The form control is DateField. It is a popover calendar on a wide viewport, and a native <input type="date"> below 768px. The switch is a width media query, not touch detection. The list cell is DateCell.

The list filter builder gives the field a native date input. It offers the same eight operators a number gets. It sends the YYYY-MM-DD string straight through.

.admin(config) sets the rest of the control. It appears on the field once @questpie/admin is enabled. Its generated signature takes unknown, so nothing type-checks the keys you pass.

Every key you pass is copied onto the control. So format reaches the picker even though the type never declares it. It is a date-fns pattern and defaults to PP. Keys such as showInList, listWidth, sortable and filterable come from the base admin config that every field type shares.

Lists of dates

.array() replaces the date column with jsonb. It also swaps the eleven operators for the array set. Every range comparison goes. What is left is containsAll, containsAny, eq, length, isEmpty, isNotEmpty, isNull and isNotNull. eq now takes the whole list. .minItems(n) and .maxItems(n) bound it. Each item still validates as YYYY-MM-DD.

blackoutDates: f.date().array().maxItems(20),

The date control does not survive the wrap. The admin's array control knows text, textarea, number, email and select. A list of dates falls back to plain text inputs.

Arrays has the operator table that replaces this one.

Types

A date field contributes string to the row, the insert and the where. .required() makes it non-null and mandatory on insert. .default("2026-01-01") makes the input optional again, and the literal type-checks against string. .autoNow() does the same at runtime, but not in the type.

type Announcement = typeof announcements.$infer.select;
//   ^? { id: string; validFrom: string; validTo: string | null; ... }

import type { CollectionDoc, CollectionWhere } from "#questpie";

type Announcement = CollectionDoc<"announcements">;
type AnnouncementFilter = CollectionWhere<"announcements">;

Related

Temporal values is the contract for what crosses the wire, through realtime and into SSR.

f.datetime() is the instant, a Date in a timestamp(3) with time zone.

f.time() is the clock without the day.

Fields is the table of every type and the modifiers they all share.

Arrays covers .array() on any field.

Validation covers the derived schema and .zod(), the way to add a rule the type does not carry.