Android Question Header/Details - best practice to store

Bobi · Jun 29, 2015

What is the best practice to work with Header/Details document structure from real world (using for example type)?

B4X:

    Type Order (id_order As Int, od As OrderDetail)
Type OrderDetail (id_orderdetail, id_order As Int)

This is not a solution because i have there a one-to-many relation.

Thank you

eurojam · Jun 29, 2015

This sounds like a database solution where you can easily manage 1:many relations. If you want to make it without a database, i would choose a list:

B4X:

Type Order (id_order As Int, OrderDetailList As List)

where you put the details in the list of your type....

Bobi · Jun 29, 2015

eurojam said:
This sounds like a database solution where you can easily manage 1:many relations. If you want to make it without a database, i would choose a list:

B4X:

Type Order (id_order As Int, OrderDetailList As List)

where you put the details in the list of your type....

So do you suggest to append (type of) OrderDetails to list. Seems to be a nice aproach.

eurojam · Jun 29, 2015

yes, but I would regard the database as the first choice.

Bobi · Jun 29, 2015

eurojam said:
yes, but I would regard the database as the first choice.

Sure. But not in my case. All information resides in a database behind an web services. Mobile application is just a ... window where I can see/manipulate data. It's not working "offline" so I don't need to store data. Hope puting some information in memory it's not a tragedy

Android Question Header/Details - best practice to store

Bobi

Member

eurojam

Well-Known Member

Bobi

Member

eurojam

Well-Known Member

Bobi

Member

Similar Threads

Android Question Header/Details - best practice to store

Bobi

Member

eurojam

Well-Known Member

Bobi

Member

eurojam

Well-Known Member

Bobi

Member

Similar Threads

Privacy & Transparency

Privacy & Transparency