[[BackLinksMenu]]

[[TicketQuery(summary=S2S_PERSISTENCE_COMMONS_R0, compact)]]


= Analysis =
^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^

== Overview ==
There will be singleton class that will provide the connections and communications with the database. There will be Data Access Objects that 
represent the persistence layer and communicate with the database. They will persist, update, delete and retrieve the objects used by the service and view layers. The scheme of the database will be created and used from the DAO(Data Access Object)s.

== Task requirements ==
Create the manager that communicates with the database.
Create the DAOs that will be needed from the other tasks in this revision.
Create the database schema to the extend needed by the other tasks in R0

We must decide if we will have opened connection all the time or for every action to the database we will open a connection.

== Task result ==
The end result will be interface for communication with the database. The DAO objects will use the connection to the DB
provided by the database manager and will be used directly only by the services. The DAO object will create queries to the database like:
{{{
SELECT FROM USER password where username={?}
}}} 

== Implementation idea ==
The DAOs will be singleton that execute queries to the database using the DatabaseManager which is also singleton. The singleton
design pattern is used because of the many queries that will be executed at a time. 

== Related ==
^(Here you can add related tasks that could be useful or helpful.)^

== How to demo ==
There will be JUnit tests for that task. The DAOs will be used by the service layer.

= Design =

= Implementation =
^(Implementation results should be described and linked here (from the wiki or the repository))^

= Testing =

= Comments =
^(Write comments for this or later revisions here.)