like in most of the applications that consist on getting, transforming and moving data, the Data Base is one critical point in this application.
The model that I have implemented is similar to a Star Model used in DataWarehousing, it has one main facts table, in this case the Outlay Table, and several Dimension Tables. This is not a DataWarehouse but currently I am working in this subject and now I only see star models :). The "Dimension" Tables can be
The Outlay will store the Charge of each Outlay, the Date of the Transaction, and the Account. This table will be related with:
- ItemsTable where the items and types are stored.
-Account that is relatedwuth currency.
-Places and Adress are separated, Firstly there were connected. The idea was to have for a place (store, ATM, Restauran) different Addresses like Taco Bell in the street foo and the Taco Bell of the street foofoo, But I am thinking on how to link them, because maybe in the same "address" can be 2 different places, like in a mall, different stores but the same address.
-Album that is connected with Files Table. So one outlay has an album of files/photos/etc and each file can be linked to different outlays.
This DataBase reduce the space of disk used. It keeps away the basic information of each outlay and maintain grouped the common data.
I have use for the diagram LucidChart Chrome Applicaction. .
For the development after looking in some books, I found this useful tutorial
With this one I learned how to access the data from the console.
When I needed more "usability" to see the database I export the database from the "android view" on eclipse:
file explorer, /data/data/
Here the model:
No hay comentarios:
Publicar un comentario