Fix a small bug of gdrop

This commit is contained in:
suxunbin 2018-11-18 19:30:56 +08:00
parent 1e0d96c042
commit e9e4b3f5e3
3 changed files with 12 additions and 7 deletions

View File

@ -39,12 +39,11 @@ int main(int argc, char * argv[])
{
cout << "The database that you want to drop does not exist." << endl;
return -1;
}
};
//delete database information in system.db
Database system_db("system");
system_db.load();
string sparql = "DELETE WHERE {<" + db_name + "> ?x ?y.";
string sparql = "DELETE WHERE {<" + db_name + "> ?x ?y.}";
ResultSet _rs;
FILE* ofp = stdout;
string msg;

View File

@ -342,7 +342,7 @@ If you want to restore the initial configuration of the ghttp server, type `bin/
#### 14. test utilities
A series of test program are placed in the `scripts/` folder, and we will introduce the several useful ones: `full_test.sh`, `basic_test.sh`, `update_test.cpp`, `dataset_test.cpp` and `gtest.cpp`.
A series of test program are placed in the `scripts/` folder, and we will introduce the several useful ones: `full_test.sh`, `basic_test.sh`, `update_test.cpp`, `parser_test.sh`, `dataset_test.cpp` and `gtest.cpp`.
**`full_test.sh` is used to compare the performance of gStore and other database systems on multiple datasets and queries.**
@ -354,7 +354,7 @@ Only gStore and Jena are tested and compared in this script, but it is easy to a
Just run `bash scripts/basic_test.sh` to use this script.
In fact, `make test` will conduct `basic_test.sh` above and `update_test.cpp` below.
In fact, `make test` will conduct `basic_test.sh` above, `update_test.cpp` and `parser_test.sh` below.
You are advised to finish this verification each time after you add some modifications and compile again(including the case that you update the code using `git pull`).
@ -373,6 +373,10 @@ bin/update_test ${YOUR_GROUP_NUMBER} ${YOUR_GROUP_SIZE} > /dev/null
```
**`parser_test.sh` is used to verify the correctness of parser.**
Just run `bash scripts/parser_test.sh` to use this script.
**`dataset_test.cpp` is used to verify the correctness of build/query on several big datasets.**
If you want to test the correctness of build/query on the big datasets, you can find `dataset_test` executable under the `scripts/` directory after you compile the whole project with `make`.

View File

@ -531,10 +531,12 @@ $(api_java):
.PHONY: clean dist tarball api_example gtest sumlines contribution test
test: $(TARGET)
@echo "basic build/query/add/sub/drop test"
@echo "basic build/query/add/sub/drop test......"
@bash scripts/basic_test.sh
@echo "repeatedly insertion/deletion test"
@echo "repeatedly insertion/deletion test......"
@bin/update_test > /dev/null
@echo "parser test......"
@bash scripts/parser_test.sh
clean:
#rm -rf lib/libantlr.a