Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 most recent events by user sqweek occurring on or after 2021-12-17 03:24:48.
|
2023-03-10
| ||
| 04:40 | • Reply: CLI option processing request artifact: a383d242b4 user: sqweek | |
|
2023-02-27
| ||
| 01:57 | • Reply: Feature suggestion: local .sqliterc discovery artifact: a5980d2a41 user: sqweek | |
|
2023-02-01
| ||
| 09:39 | • Reply: xCheckReservedLock spec vs. implementation artifact: 8dc90911b9 user: sqweek | |
|
2023-01-30
| ||
| 05:39 | • Reply: feature suggestion Prepared statements in SQL: PREPARE/EXECUTE/DEALLOCATE PREPARE statements artifact: ce0a288fd5 user: sqweek | |
|
2023-01-23
| ||
| 07:01 | • Reply: MEMSYS5 not fully reserving the memory? artifact: f8d772ecd0 user: sqweek | |
|
2023-01-20
| ||
| 05:30 | • Reply: One base and several applications artifact: 18ec619f31 user: sqweek | |
|
2023-01-19
| ||
| 04:46 | • Reply: Completion of error handling artifact: 6d197e913f user: sqweek | |
| 03:20 | • Reply: cross-compiling to Windows host on Linux builder: can't find ioctl.h artifact: 7adb461e70 user: sqweek | |
|
2023-01-06
| ||
| 04:28 | • Reply: Ctrl-Z too pretty for published Linux 3.40.1 CLI artifact: b54969e335 user: sqweek | |
|
2023-01-05
| ||
| 06:31 | • Reply: Ctrl-Z too pretty for published Linux 3.40.1 CLI artifact: 25942ecacd user: sqweek | |
|
2022-12-19
| ||
| 03:50 | • Reply: PRAGMA comands and how to prevent database corruption artifact: 53bcae45f6 user: sqweek | |
|
2022-12-16
| ||
| 04:53 | • Reply: An INTEGER value is less than any TEXT value... but sometimes not artifact: be4cdaad8a user: sqweek | |
|
2022-12-15
| ||
| 05:05 | • Reply: Are SQLite schema changes intended to be transactional? artifact: 7d5658b52d user: sqweek | |
| 04:25 | • Reply: Are SQLite schema changes intended to be transactional? artifact: d025322e74 user: sqweek | |
|
2022-12-09
| ||
| 04:48 | • Reply: Are SQLite schema changes intended to be transactional? artifact: 7a6e602e14 user: sqweek | |
|
2022-12-02
| ||
| 03:54 | • Reply: SQLite3 is far too tolerant of broken text data artifact: 617cfabe03 user: sqweek | |
| 03:12 | • Reply: SQLite3 is far too tolerant of broken text data artifact: 153fb89703 user: sqweek | |
|
2022-11-28
| ||
| 05:05 | • Reply: Does an unchanged DB retain its timestamp? artifact: 35de61064c user: sqweek | |
|
2022-11-24
| ||
| 02:04 | • Reply: How to perform SQLite3 realtime incremental backup. artifact: d575f69ea3 user: sqweek | |
|
2022-11-11
| ||
| 02:43 | • Reply: ENOTABUG Bug report: default journal_mode seems to delete journal without checking status artifact: aa0912ad80 user: sqweek | |
|
2022-11-10
| ||
| 07:07 | • Reply: Why is the return code 17 (and not 1)? artifact: 9b376465d4 user: sqweek | |
| 05:05 | • Reply: ENOTABUG Bug report: default journal_mode seems to delete journal without checking status artifact: deb62ed71d user: sqweek | |
|
2022-11-04
| ||
| 11:57 | • Reply: Problem with sqlite3 (CLI): Error: too many options artifact: 1b1c7a2810 user: sqweek | |
|
2022-11-03
| ||
| 08:00 | • Reply: documentation of temporary files... artifact: 76837209c8 user: sqweek | |
|
2022-10-07
| ||
| 16:30 | • Edit reply: Does the design of deferred transactions lead to deadlocks? artifact: 2a46091f43 user: sqweek | |
| 16:28 | • Reply: Does the design of deferred transactions lead to deadlocks? artifact: cb8d2d7208 user: sqweek | |
| 03:11 | • Reply: Does the design of deferred transactions lead to deadlocks? artifact: 2dfadab628 user: sqweek | |
|
2022-09-29
| ||
| 07:13 | • Reply: 3.39.3 resolving all symbolic links in database filenames to create a canonical name breaks existing application artifact: 15d686acf9 user: sqweek | |
| 06:55 | • Reply: 3.39.3 resolving all symbolic links in database filenames to create a canonical name breaks existing application artifact: 22e1c8ccc2 user: sqweek | |
| 06:33 | • Reply: Script to wrap backup commands artifact: 1b0a169cf4 user: sqweek | |
| 03:23 | • Reply: Avoiding SQLITE_BUSY between a producer process (db writing) and consumer process (db reading) artifact: 2208d759b7 user: sqweek | |
| 02:56 | • Reply: Avoiding SQLITE_BUSY between a producer process (db writing) and consumer process (db reading) artifact: 6f595f12db user: sqweek | |
|
2022-09-12
| ||
| 08:21 | • Reply: SQLite integrity check=ok but data corrupted artifact: 2bb1709c12 user: sqweek | |
|
2022-09-05
| ||
| 03:51 | • Reply: Simultaneous read and write transactions: when they can commit? artifact: b07f569857 user: sqweek | |
|
2022-08-17
| ||
| 14:39 | • Reply: (Deleted) artifact: d68bf7105d user: sqweek | |
|
2022-06-30
| ||
| 09:41 | • Reply: Besides the page, what is SQLite flushing? artifact: 085de7f03f user: sqweek | |
| 07:11 | • Reply: 'image is malformed' in in-memory database artifact: 7faf1d2b9e user: sqweek | |
| 04:49 | • Reply: Besides the page, what is SQLite flushing? artifact: 6d8d6b4843 user: sqweek | |
|
2022-06-23
| ||
| 15:57 | • Reply: Can I reserve database space to keep it working on zero fs free space? artifact: f090cc7d2a user: sqweek | |
|
2022-03-31
| ||
| 10:03 | • Reply: some weird date side effects artifact: 13a3f924df user: sqweek | |
|
2022-03-28
| ||
| 07:48 | • Reply: How to escape parameters artifact: a6c4d7ec9d user: sqweek | |
|
2022-03-22
| ||
| 14:43 | • Reply: Write locking and subqueries artifact: e46eb2a195 user: sqweek | |
|
2022-03-10
| ||
| 03:40 | • Reply: Switching between EXCLUSIVE and NORMAL lock mode for backup artifact: 1d780acf33 user: sqweek | |
|
2022-03-03
| ||
| 17:58 | • Reply: Switching between EXCLUSIVE and NORMAL lock mode for backup artifact: 866bf3407a user: sqweek | |
|
2022-02-15
| ||
| 09:01 | • Reply: What is going on here? (unexplainable behaviour) artifact: ecdf653f21 user: sqweek | |
|
2022-02-07
| ||
| 01:58 | • Reply: BUG: '--' not literal? artifact: 68fc25267d user: sqweek | |
| 01:51 | • Reply: BUG: '--' not literal? artifact: a1ab64de90 user: sqweek | |
|
2022-01-13
| ||
| 21:51 | • Reply: Unable to read while database is locked artifact: 474e6c3806 user: sqweek | |
|
2021-12-30
| ||
| 09:55 | • Reply: Serious error emptied my complete database! artifact: 9851ce24d6 user: sqweek | |
|
2021-12-17
| ||
| 03:24 | • Reply: Trying to "Open Database" Safari History.db file and get Error: "could not open safari database file reason: unable to open.. artifact: d264a96f01 user: sqweek | |