Skip to content

fix: use (unixepoch('subsecond') * 1000) to get proper precision of timestamp #606

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −4
Open

fix: use (unixepoch('subsecond') * 1000) to get proper precision of timestamp #606

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/content/docs/guides/timestamp-default-value.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,7 +267,7 @@ export const users = sqliteTable('users', {
.default(sql`(unixepoch())`),
timestamp2: integer('timestamp2', { mode: 'timestamp_ms' })
.notNull()
.default(sql`(unixepoch() * 1000)`),
.default(sql`(unixepoch('subsecond') * 1000)`),
timestamp3: integer('timestamp3', { mode: 'number' })
.notNull()
.default(sql`(unixepoch())`),
Expand All @@ -278,7 +278,7 @@ export const users = sqliteTable('users', {
CREATE TABLE `users` (
`id` integer PRIMARY KEY NOT NULL,
`timestamp1` integer DEFAULT (unixepoch()) NOT NULL,
`timestamp2` integer DEFAULT (unixepoch() * 1000) NOT NULL,
`timestamp2` integer DEFAULT (unixepoch('subsecond') * 1000) NOT NULL,
`timestamp3` integer DEFAULT (unixepoch()) NOT NULL
);
```
Expand All @@ -293,7 +293,7 @@ The difference is that `timestamp` handles seconds, while `timestamp_ms` handles
+------------+------------+---------------+------------+
| id | timestamp1 | timestamp2 | timestamp3 |
+------------+------------+---------------+------------+
| 1 | 1712835640 | 1712835640000 | 1712835640 |
| 1 | 1712835640 | 1712835640469 | 1712835640 |
+------------+------------+---------------+------------+
```

Expand All @@ -303,7 +303,7 @@ The difference is that `timestamp` handles seconds, while `timestamp_ms` handles
{
id: 1,
timestamp1: 2024-04-11T11:40:40.000Z, // Date object
timestamp2: 2024-04-11T11:40:40.000Z, // Date object
timestamp2: 2024-04-11T11:40:40.469Z, // Date object
timestamp3: 1712835640 // number
}
]
Expand Down