Tag Info

New answers tagged

1

The documentation says: Indices are not required for child key columns but they are almost always beneficial. Each time an application deletes a row from the parent table, it performs [some query]. If this SELECT returns any rows at all, then SQLite concludes that deleting the row from the parent table would violate the foreign key constraint and ...


0

I would go with the single-table option. It's simpler and I don't see any reason why you would need two tables in this case. If you want to make it easier to find records with status of "2" or "3", you could create a view that only displays these. The only reason I could see for having two tables is if inserting/updating with a BLOB is very slow and causes ...


1

Maybe you don't expect this answer, but do both. Let's see. In order to accomodate for the life-cycle of the data ( something many database designers don't contemplate ), you should have a "historic" table with the downloads that finished. That table will not only hold files that downloaded successfully to a 100%, but also downloads that were canceled or ...


2

First, is it true that the ideal implementation for bulk storage is to use a flat file database? If you're talking about SQLite, it isn't a "flat file database". Sure, it's a single file database, but it's highly structured. Second, is it true that for concurrent reads & writes, PostgreSQL vastly outperforms a flat file database? PostgreSQL ...



Top 50 recent answers are included