News for hackers. Stuff that matters.
Re:SQLite 3.32 by gwbas1c on Saturday May 23, 2020 @10:05AM (#23283019)
I just sucked the existing table into RAM and recreated the table. I did it on a transaction so there was no risk of data loss.

In my case the data was always 10s of MBs.

Remember, the point of SQLite is a replacement for generating a file format. Although it's a database, it lets us (developers) re-use our knowledge of databases when doing basic file I/O.

Re:SQLite 3.32 by 72deluxe on Saturday May 23, 2020 @01:11PM (#23284608)
How does dropping the existing table and recreating it affect FKs pointing to the table that is being dropped??

Do the FK relationships get destroyed??

Re:SQLite 3.32 by kcolford on Saturday May 23, 2020 @02:40PM (#23285310)
You gotta redo the foreign key constraints in the same transaction that you rebuild the table
Re:SQLite 3.32 by 72deluxe on Wednesday May 27, 2020 @05:49AM (#23321205)
Oh so specify the FKs from table B to A (if we were dropping and rebuilding A) in a begin/end transaction block?

Thank you

Re:SQLite 3.32 by gwbas1c on Sunday May 24, 2020 @12:35PM (#23292643)
In my case foreign keys were enforced in the application business logic. The schema was extremely simple.