On 2 September 2011 13:08, LiTTle <[email protected]> wrote: > There 2 reasons I didn't use database:
There are 2 reasons why you should consider it: > 1. I cannot imagine a helpful scheme of tables to use! ...that does not mean that such schema does not exist. Your data model will depend on what data you store and how you use (create, modify and retrieve) all that data. Your solution will certainly have troubles scaling and staying consistent. Manually updating anything will cause problems, even when people know what they are doing. What do you envisage to happen, once a shop has been modified or added? Release new app? Can you predict how many updates or addition will happen once the app is in the wild? > 2. I want my colleagues to have the ability to add new shops easily! > It's easier to tell them to do some copy-paste work. In case I use db > they have to download a db browser, execute any sql command (if > needed) etc. How about hosting a CRUD web-app to manage your data stored centrally in a DB with periodic updates to local DBs on each client? > My current design is: > assets > Category_Car > Rent.xml > Repair.xml > Category_Education > Libraries.xml > > It is working just fine! Any idea about a db scheme is accepted! I > hope that I don't waste your time. any data design takes a bit more input than this. -- Daniel Drozdzewski -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
