aibarbetta / database

Trabajo Práctico 2 - 75.59 Técnicas de Programación Concurrente I (FIUBA)

DataBase

Trabajo Práctico 2 - 75.59 Técnicas de Programación Concurrente I (FIUBA)

Build

To build the project you can use the script

$ ./build.sh

This will create a build directory with the server and client executables.

Command line arguments

Server

• DB file
  Database persistence file.

Client

The client takes no arguments

Execution examples

Server

$ ./build/server build/db.txt

Client

$ ./build/client

Usage

Make a query (insert <name,address,phone>, select <name,address,phone>) or just exit.
> insert Sherlock Holmes,Baker Street 221B,58859989
Success
> select sherlock holmes,,
1 results.
Sherlock Holmes,Baker Street 221B,58859989
>
> exit

License

GNU General Public License v3.0

database's Issues

Create a separate class responsible of the Database

It should load the database from file, mantain it in memory and when the server finishes write it to a file for persistency. And test it 😁 (#7 )

Test usage with multiple clients

Add validations for string sizes on server side

• name <= 61 B
• address <= 130 B
• phone <= 13 B

README

Create Lock class

Shared and Exclusive locks as needed

Classes diagrams

Implement Server responses

• Send response after insertion operation.
• Send response and registers after get operation.

Fix query parsing on select operation

Test insert method

Remember to check case where a duplicated register is inserted (it should fail)

Fix Client::get_entry as it only receives a name

The GET operation on the server allows to filter based on many parameters besides the name of the register. Right now the method doesn't support this

Create database class

Upgrade client's CLI for interacting with the server

Test data persistency of the database

After the Server shutdowns it should persist all the database information on a file.

Implement database persistence in separate class

The server shouldn't have the responsibility to know how to persist the database into a file.

Queue::pop should receive msgtype

Also check if msgrcv is blocking

Handle queue creation and destruction

Create and destroy queue on father process (possibly Server process)

Refactor struct Query

The Query should support both messages to the Server and to the Client. So it should be named Message (and modified accordingly) as it is more appropriate.

It should also be refactored as it's shown in the attached image.