Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
111 events occurring around 0fe2300d3fa65c4e.
|
2020-07-23
| ||
| 14:51 | • Reply: alter table "table" add column "name" varchar not null throws Cannot add a NOT NULL column with default value NULL artifact: fd69e1b4de user: juslintek | |
| 14:39 | • Reply: alter table "table" add column "name" varchar not null throws Cannot add a NOT NULL column with default value NULL artifact: 62416c35b0 user: stephan | |
| 14:31 | • Post: alter table "table" add column "name" varchar not null throws Cannot add a NOT NULL column with default value NULL artifact: 17ebad32a5 user: juslintek | |
| 14:26 | • Edit reply: GCC-7 and later miscompile SQLite artifact: fa66580299 user: LarryBrasfield | |
| 13:57 | • Reply: facing issue from sqlite3_step() artifact: 1277f59acf user: JLHainaut | |
| 13:46 | • Edit reply: GCC-7 and later miscompile SQLite artifact: 18b16a3120 user: Chanda | |
| 13:14 | • Edit reply: GCC-7 and later miscompile SQLite artifact: ac4d555709 user: Chanda | |
| 12:14 | • Reply: GCC-7 and later miscompile SQLite artifact: a259e3f35b user: Chanda | |
| 11:49 | • Reply: column check constraint typeof(col) = 'integer' fails if col has declared type text artifact: 420403c34d user: dvdraymond | |
| 10:50 | • Post: column check constraint typeof(col) = 'integer' fails if col has declared type text artifact: df68fc4cc9 user: anonymous | |
| 05:48 | • Reply: Crash while sqlite3_prepare_v2 with signal SIGFPE in SQLite version 3.31.01 artifact: 19a106df2e user: stephan | |
| 05:27 | • Reply: Crash while sqlite3_prepare_v2 with signal SIGFPE in SQLite version 3.31.01 artifact: b251e90e89 user: RomioGeek | |
| 02:08 | • Reply: Password-protected databases no longer work with 1.113, no rollback possible artifact: a8c99c68e1 user: nandostyle | |
| 02:05 | • Reply: Password-protected databases no longer work with 1.113, no rollback possible artifact: b2d26ab3da user: nandostyle | |
|
2020-07-22
| ||
| 20:11 | • Edit: sessionfuzz fails on some architectures (ARM, PPC, SPARC) artifact: d44eb2fc44 user: Arfrever | |
| 19:14 | • Post: sessionfuzz fails on some architectures (ARM, PPC, SPARC) artifact: 6c501b1e70 user: Arfrever | |
| 14:55 | • Reply: GCC-7 and later miscompile SQLite artifact: f62185e4e2 user: LarryBrasfield | |
| 09:11 | • Reply: GCC-7 and later miscompile SQLite artifact: 63062bb261 user: Chanda | |
| 06:09 | • Reply: facing issue from sqlite3_step() artifact: 2413c2d7fc user: gunter_hick | |
|
2020-07-21
| ||
| 18:52 | • Post: GCC-7 and later miscompile SQLite artifact: 54e1773c0c user: drh | |
| 16:17 | • Reply: Crash while sqlite3_prepare_v2 with signal SIGFPE in SQLite version 3.31.01 artifact: 6009b7b9de user: LarryBrasfield | |
| 14:14 | • Reply: how to check update statement really modify a record artifact: 8e23cd7351 user: gunter_hick | |
| 10:41 | • Edit reply: Crash while sqlite3_prepare_v2 with signal SIGFPE in SQLite version 3.31.01 artifact: a89ab00bf3 user: drh | |
| 10:40 | • Edit: Crash while sqlite3_prepare_v2 with signal SIGFPE in SQLite version 3.31.01 artifact: 1c83b5f9b8 user: drh | |
| 10:05 | • Reply: Crash while sqlite3_prepare_v2 with signal SIGFPE in SQLite version 3.31.01 artifact: 328565c6b0 user: RomioGeek | |
| 09:02 | • Post: Crash while sqlite3_prepare_v2 with signal SIGFPE in SQLite version 3.31.01 artifact: f868213e55 user: RomioGeek | |
|
2020-07-20
| ||
| 23:47 | • Reply: facing issue from sqlite3_step() artifact: 782387540d user: kmedcalf | |
| 17:58 | • Reply: Error message that is not an error!!! artifact: 2058db3ef2 user: dvdraymond | |
| 17:37 | • Post: Error message that is not an error!!! artifact: ab90954499 user: pizzipie | |
| 17:15 | • Post: Typo in Quirks documentsection 6 artifact: 77ecdf444f user: RichardBWE | |
| 13:36 | • Reply: Possible bug in .read when a directory is specified? artifact: a1a20b22e4 user: luuk | |
| 07:53 | • Reply: facing issue from sqlite3_step() artifact: 71b74ef7ff user: ddevienne | |
| 07:27 | • Reply: facing issue from sqlite3_step() artifact: 6cea8da388 user: prajeeshprakashp | |
| 05:35 | • Reply: Possible bug in .read when a directory is specified? artifact: 7d0704a798 user: sqweek | |
|
2020-07-19
| ||
| 21:40 | • Reply: Multiple tables artifact: f5655c8da1 user: ingo | |
| 20:56 | • Reply: Multiple tables artifact: 941f3c2b7d user: joey8joey8 | |
| 14:46 | • Edit reply: Multiple tables artifact: 499a402fe3 user: joey8joey8 | |
| 14:18 | • Reply: Possible bug in .read when a directory is specified? artifact: a566761b6a user: anonymous | |
| 13:05 | • Reply: Multiple tables artifact: 4d4111c665 user: ingo | |
| 09:05 | • Reply: Multiple tables artifact: d467c9b212 user: joey8joey8 | |
| 07:28 | • Reply: Multiple tables artifact: 9467553ef2 user: ingo | |
|
2020-07-18
| ||
| 23:13 | • Reply: Multiple tables artifact: 02bf84ab07 user: joey8joey8 | |
| 07:52 | • Reply: Possible bug in .read when a directory is specified? artifact: 964ec34184 user: luuk | |
| 07:05 | • Reply: Password-protected databases no longer work with 1.113, no rollback possible artifact: b5cd7310ba user: anonymous | |
|
2020-07-17
| ||
| 23:59 | • Reply: UPDATE in version 3.33 artifact: ad0a86c79e user: decalek | |
| 22:06 | • Reply: UPDATE in version 3.33 artifact: 79f4d73685 user: anonymous | |
| 21:14 | • Reply: SELECT using variables artifact: 8b7074d0d0 user: TripeHound | |
| 21:10 | • Reply: UPDATE in version 3.33 artifact: c90001b4a5 user: drh | |
| 19:33 | • Reply: SELECT using variables artifact: 814bd40778 user: LarryBrasfield | |
| 18:37 | • Reply: SELECT using variables artifact: 6848942e8a user: dvdraymond | |
| 18:04 | • Reply: SELECT using variables artifact: e9ce2d8720 user: wyoung | |
| 18:01 | • Edit reply: SELECT using variables artifact: 76e32599a9 user: wyoung | |
| 17:48 | • Edit reply: Possible bug in .read when a directory is specified? artifact: 2e3990d86b user: stephan | |
| 17:43 | • Edit reply: Possible bug in .read when a directory is specified? artifact: 0f2134a219 user: stephan | |
| 17:37 | • Reply: Possible bug in .read when a directory is specified? artifact: a36dcbef66 user: stephan | |
| 17:26 | • Reply: SELECT using variables artifact: 0fe2300d3f user: wyoung | |
| 17:19 | • Reply: Possible bug in .read when a directory is specified? artifact: dd0f21df21 user: wyoung | |
| 14:07 | • Edit reply: SELECT using variables artifact: 95b98ab38a user: dvdraymond | |
| 13:42 | • Reply: Possible bug in .read when a directory is specified? artifact: ca1554dfd0 user: anonymous | |
| 12:33 | • Reply: SELECT using variables artifact: 3991d1eeda user: dvdraymond | |
| 10:55 | • Post: Bug report: broken links on sqlite.org artifact: 143c38165e user: anonymous | |
| 04:20 | • Reply: How to upgrade sqlite in cordova-sqlite-storage artifact: 6d48932bcf user: dinesh.shrinath | |
| 00:52 | • Reply: SQLITE_HAS_CODE is gone? artifact: 7d7f6633f1 user: RandomCoder | |
|
2020-07-16
| ||
| 20:40 | • Reply: SELECT using variables artifact: 5cd84a92cb user: LarryBrasfield | |
| 20:28 | • Post: SELECT using variables artifact: f4cf2b30c8 user: anonymous | |
| 20:04 | • Reply: SQLITE_HAS_CODE is gone? artifact: 597cb33cc7 user: wyoung | |
| 19:50 | • Reply: SQLITE_HAS_CODE is gone? artifact: bdf1defeb8 user: jchd18 | |
| 19:18 | • Reply: SQLITE_HAS_CODE is gone? artifact: 8062cdcd1b user: wyoung | |
| 19:05 | • Reply: SQLITE_HAS_CODE is gone? artifact: 2c5d8f6203 user: wyoung | |
| 18:56 | • Reply: SQLITE_HAS_CODE is gone? artifact: 9bcbf50147 user: jchd18 | |
| 18:47 | • Edit reply: how to check update statement really modify a record artifact: 446684b1f3 user: kmedcalf | |
| 18:46 | • Reply: how to check update statement really modify a record artifact: c10b16a491 user: dvdraymond | |
| 18:06 | • Reply: how to check update statement really modify a record artifact: 0744dd81dc user: stephan | |
| 17:58 | • Reply: Possible bug in .read when a directory is specified? artifact: 7a10ca518d user: stephan | |
| 17:50 | • Post: Possible bug in .read when a directory is specified? artifact: 4c53c434ca user: lcarlp | |
| 17:48 | • Reply: how to check update statement really modify a record artifact: cf1a8a06e8 user: doug9forester | |
| 17:40 | • Reply: how to check update statement really modify a record artifact: 574c8b134d user: kmedcalf | |
| 17:07 | • Reply: how to check update statement really modify a record artifact: 49284abed2 user: stephan | |
| 17:00 | • Reply: how to check update statement really modify a record artifact: 1b91a349e0 user: cuz | |
| 16:18 | • Reply: how to check update statement really modify a record artifact: c7ab1357f2 user: stephan | |
| 16:03 | • Reply: how to check update statement really modify a record artifact: b7913b7ad0 user: cuz | |
| 15:37 | • Reply: UPDATE in version 3.33 artifact: 00ab2253aa user: kmedcalf | |
| 13:37 | • Reply: Access sqlite database from user function artifact: 92fb1fa2e8 user: kmedcalf | |
| 13:18 | • Reply: UPDATE in version 3.33 artifact: d970a97db7 user: kmedcalf | |
| 09:05 | • Reply: Missing link in SQL documentation root to transaction artifact: 8afb66b028 user: anonymous | |
| 07:38 | • Post: Access sqlite database from user function artifact: 0865192e81 user: anonymous | |
| 07:34 | • Reply: Arithmetic errors artifact: a2f4b3f37f user: anonymous | |
| 06:26 | • Reply: UPDATE in version 3.33 artifact: 999a9d047f user: anonymous | |
| 04:34 | • Reply: UPDATE in version 3.33 artifact: 1dc831b0d2 user: dempson | |
| 04:29 | • Reply: facing issue from sqlite3_step() artifact: ae8e31863e user: kmedcalf | |
| 04:19 | • Edit reply: UPDATE in version 3.33 artifact: 41017a8da1 user: kmedcalf | |
| 04:15 | • Reply: UPDATE in version 3.33 artifact: f8d22cbae9 user: kmedcalf | |
| 03:46 | • Reply: facing issue from sqlite3_step() artifact: 7fc3597e03 user: itandetnik | |
| 02:40 | • Post: facing issue from sqlite3_step() artifact: d109f60409 user: prajeeshprakashp | |
| 02:33 | • Reply: PSTOKEN extension artifact: b1bd78c5e5 user: anonymous | |
| 02:10 | • Reply: how to check update statement really modify a record artifact: 1e8160d290 user: anonymous | |
| 01:59 | • Reply: UPDATE in version 3.33 artifact: f771fc8c47 user: anonymous | |
|
2020-07-15
| ||
| 23:58 | • Reply: how to check update statement really modify a record artifact: 9bc993e320 user: stephan | |
| 23:16 | • Reply: how to check update statement really modify a record artifact: c6f664ae6f user: kmedcalf | |
| 22:59 | • Reply: how to check update statement really modify a record artifact: 7c0e18a2e4 user: kmedcalf | |
| 21:26 | • Reply: how to check update statement really modify a record artifact: 4048b0f09e user: slavin | |
| 20:24 | • Post: UPDATE in version 3.33 artifact: fe59966950 user: anonymous | |
| 17:47 | • Reply: how to check update statement really modify a record artifact: ced02be52d user: dvdraymond | |
| 17:40 | • Reply: how to check update statement really modify a record artifact: c7d049eb72 user: stephan | |
| 17:32 | • Reply: System.Data.SQLite.Core for .Net artifact: 36bc5f5fb2 user: stephan | |
| 17:31 | • Reply: how to check update statement really modify a record artifact: 9d7e6cfbe1 user: cuz | |
| 17:11 | • Post: System.Data.SQLite.Core for .Net artifact: 91b8524eb5 user: nandostyle | |
| 16:58 | • Reply: Endianness help artifact: 30f2c372d9 user: curmudgeon | |
| 14:53 | • Reply: how to check update statement really modify a record artifact: 51b803fa78 user: stephan | |
| 14:46 | • Reply: how to check update statement really modify a record artifact: fec968b57c user: doug9forester | |
| 14:38 | • Reply: When using sqlite3_step(stmt) inside a transaction my busy-handler is not being called artifact: 8845210cdb user: kmedcalf | |