db: build a new db first then overwrite the old one
commita8d29e1de16fbe7612a0ecf0a9c31c54e3ece034
authorDan Carpenter <dan.carpenter@oracle.com>
Wed, 19 Nov 2014 14:03:03 +0000 (19 17:03 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Wed, 19 Nov 2014 14:03:03 +0000 (19 17:03 +0300)
treea7aa8faae61947bbb53e2402f039b115bfb74d12
parenta818d1ee51d465da606a83f6b5b1c9223ade669e
db: build a new db first then overwrite the old one

In the old code, it deleted the old db and rebuilt it in place.  Now we
build smatch_db.sqlite.new and then move it to smatch_db.sqlite after it's
built.

The old way was annoying because you couldn't use the database for the hour
and a half while the database was being built.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch_data/db/create_db.sh
smatch_data/db/fill_db_caller_info.pl
smatch_data/db/fill_db_sql.pl
smatch_data/db/fill_db_type_size.pl
smatch_data/db/fill_db_type_value.pl
smatch_data/db/fixup_all.sh
smatch_data/db/fixup_kernel.sh
smatch_data/db/mark_function_ptrs_searchable.pl
smatch_data/db/remove_mixed_up_pointer_params.pl