Gstore System(also called gStore) is a graph database engine for managing large graph-structured data, which is open-source and targets at Linux operation systems. The whole project is written in C++, with the help of some libraries such as readline, antlr, and so on. Only source tarballs are provided currently, which means you have to compile the source code if you want to use our system.
The formal help document is in Handbook.
The formal experiment result is in Experiment.
We have built an IRC channel named #gStore on freenode, and you can also come to our website: gStore.
This system is really user-friendly and you can pick it up in several minutes. Remember to check your platform where you want to run this system by viewing System Requirements. After all are verified, please get this project's source code. There are several ways to do this:
-
download the zip from this repository and extract it
-
fork this repository in your github account
-
type
git clone [email protected]:Caesar11/gStore.gitin your terminal or use git GUI to acquire it
Then you need to compile the project, just type make in the gStore root directory, and all executables will be ok. To run gStore, please type bin/gbuild database_name dataset_path to build a database named by yourself. And you can use bin/gquery database_name command to query a existing database. What is more, bin/gconsole is a wonderful tool designed for you, providing all operations you need to use gStore. Notice that all commands should be typed in the root directory of gStore, and your database name should not end with ".db".
If you want to understand the details of the gStore system, or you want to try some advanced operations(for example, using the API, server/client), please see the chapters below.
-
Basic Introduction: introduce the theory and features of gStore
-
Install Guide: instructions on how to install this system
-
How To Use: detailed information about using the gStore system
-
API Explanation: guide you to develop applications based on our API
-
Project Structure: show the whole structure and sequence of this project
-
Related Essays: contain essays and publications related with gStore
-
Update Logs: keep the logs of the system updates
-
Test Results: present the test results of a series of experiments
We have written a series of short essays addressing recurring challenges in using gStore to realize applications, which are placed in Recipe Book.
You are welcome to report any advice or errors in the github Issues part of this repository, if not requiring in-time reply. However, if you want to urgent on us to deal with your reports, please email to [email protected] to submit your suggestions and report bugs to us by emailing to [email protected]. A full list of our whole team is in Mailing List.
There are some restrictions when you use the current gStore project, you can see them on Limit Description.
Sometimes you may find some strange phenomena(but not wrong case), or something hard to understand/solve(don't know how to do next), then do not hesitate to visit the Frequently Asked Questions page.
Graph database engine is a new area and we are still trying to go further. Things we plan to do next is in Future Plan chapter, and we hope more and more people will support or even join us. You can support in many ways:
-
watch/star our project
-
fork this repository and submit pull requests to us
-
download and use this system, report bugs or suggestions
-
...
People who inspire us or contribute to this project will be listed in the Thanks List chapter.
This whole document is divided into different pieces, and each them is stored in a markdown file. You can see/download the combined markdown file in help_markdown, and for html file, please go to help_html. What is more, we also provide help file in pdf format, and you can visit it in help_pdf.