Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 most recent events occurring on or after 2021-11-18 21:46:39.
2021-11-20
| ||
19:11 | • Reply: .mode html should output lowercase HTML tags (artifact: 88b14b4be7 user: nat-418) | |
17:54 | • Reply: A flat-file interface for SQLite? (artifact: 0b4ed3f2de user: anonymous) | |
17:47 | • Reply: .mode html should output lowercase HTML tags (artifact: 478127f3f2 user: UserMBL) | |
17:08 | • Post: .mode html should output lowercase HTML tags (artifact: 8b38a164bc user: nat-418) | |
17:00 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: 9f5da01ff4 user: larrybr) | |
14:52 | • Reply: A flat-file interface for SQLite? (artifact: fcbdada596 user: nat-418) | |
14:46 | • Reply: A flat-file interface for SQLite? (artifact: 0810010c3c user: nat-418) | |
14:45 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: d67d73f05b user: rouault) | |
14:38 | • Reply: A flat-file interface for SQLite? (artifact: 1589810105 user: nat-418) | |
14:31 | • Reply: A flat-file interface for SQLite? (artifact: d5e87cfb61 user: stephan) | |
13:49 | • Reply: Proposed slightly-incompatible change to date-time functions (artifact: b5b3fb365a user: RichardDamon) | |
13:29 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: 2a51131167 user: UserMBL) | |
13:23 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: c34550d653 user: drh) | |
13:22 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: d0b66d1e04 user: rouault) | |
13:16 | • Reply: A flat-file interface for SQLite? (artifact: a5dd0421d4 user: UserMBL) | |
11:41 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: 07d271b96c user: casaderobison) | |
11:35 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: 0038ebd08e user: drh) | |
11:02 | • Edit reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: 9536783178 user: rouault) | |
10:41 | • Delete reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: 6cca3702a2 user: rouault) | |
10:37 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: f988bd3d01 user: rouault) | |
09:14 | • Reply: User Define Aggregate Functions with multiple columns and scaler value (artifact: 0cbb988840 user: airen977) | |
08:28 | • Post: A flat-file interface for SQLite? (artifact: 1456d7e66d user: nat-418) | |
02:58 | • Reply: Proposed slightly-incompatible change to date-time functions (artifact: 54f40d17c9 user: drh) | |
02:49 | • Reply: Proposed slightly-incompatible change to date-time functions (artifact: 975405dad8 user: RichardDamon) | |
02:48 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: dd4d62e69a user: drh) | |
01:52 | • Reply: Hot backup database in WAL mode by coping (artifact: fa97dca4b4 user: anonymous) | |
01:28 | • Reply: Hot backup database in WAL mode by coping (artifact: 1a262ad108 user: slavin) | |
2021-11-19
| ||
22:46 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: b4e804a5d4 user: rouault) | |
22:38 | • Reply: Hot backup database in WAL mode by coping (artifact: 8dfd8df07e user: casaderobison) | |
21:56 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: 677e52a522 user: kmedcalf) | |
21:42 | • Reply: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: 5dbb5ad543 user: drh) | |
21:36 | • Reply: Hot backup database in WAL mode by coping (artifact: fc4bab4181 user: anonymous) | |
21:26 | • Reply: Hot backup database in WAL mode by coping (artifact: 7bfbc394d4 user: anonymous) | |
21:25 | • Post: IS NULL optimization on NOT NULL constraints breaks on corrupted databases (artifact: 47dae2beeb user: rouault) | |
18:33 | • Reply: Hot backup database in WAL mode by coping (artifact: ec763d9d48 user: anonymous) | |
18:20 | • Reply: Hot backup database in WAL mode by coping (artifact: 2fa9c6ac63 user: slavin) | |
17:58 | • Reply: Hot backup database in WAL mode by coping (artifact: 61cabcc8dd user: casaderobison) | |
16:57 | • Reply: Hot backup database in WAL mode by coping (artifact: 3a151087f5 user: larrybr) | |
16:53 | • Reply: Hot backup database in WAL mode by coping (artifact: dac27c959c user: anonymous) | |
16:50 | • Reply: Hot backup database in WAL mode by coping (artifact: 9e978a73dd user: anonymous) | |
16:33 | • Edit reply: Possible data race in os.unix.c:5805:unixTempFileDir (artifact: c660666202 user: larrybr) | |
15:52 | • Reply: Possible data race in os.unix.c:5805:unixTempFileDir (artifact: 5df0c6ca22 user: 0xjnml) | |
15:49 | • Reply: Proposed slightly-incompatible change to date-time functions (artifact: 6df0d89eaa user: drh) | |
14:03 | • Reply: Possible data race in os.unix.c:5805:unixTempFileDir (artifact: fe55aff7f9 user: larrybr) | |
13:31 | • Reply: Proposed slightly-incompatible change to date-time functions (artifact: 8f60de0027 user: RichardDamon) | |
13:16 | • Reply: Is it possible to restrict VACUUM INTO? (artifact: a2e181c2a9 user: drh) | |
13:07 | • Post: Proposed slightly-incompatible change to date-time functions (artifact: 92d9dbc028 user: drh) | |
12:48 | • Post: Is it possible to restrict VACUUM INTO? (artifact: 77ae0ac121 user: anonymous) | |
10:52 | • Post: Possible data race in os.unix.c:5805:unixTempFileDir (artifact: f670d7ae20 user: 0xjnml) | |
2021-11-18
| ||
21:46 | • Reply: PRINTF - newlines, tabs etc? (artifact: 0f2e119817 user: larrybr) | |