Hi, I said I'd upload an ERD of a many-to-many use case at Utah Code Camp. I'm finally getting around to it (sorry). I'm not really awesome with GitHub, so hopefully this is an acceptable place to submit this. Here it is:
My use case is an app for warehouse drivers to deliver goods to locations and receive signatures. The many-to-many comes in when we have many tickets which contain the same item. For example, pencils may be on multiple tickets, but we don't want to have pencils in the DB multiple times.
Hopefully this makes sense. I'm excited for this project, because copy/pasting a bunch of boiler plate is no fun, time consuming, hard to do right and prone to human error. I think more people would use ContentProviders if they weren't so cumbersome, and I hope Google someday writes something like the CoreData UI for building tables and relationships.
Jordan, thank you for this. This is a really helpful example for us to see how to make a useful implementation. We're actively working on this feature and it's currently one of our top priorities.
Hi, I said I'd upload an ERD of a many-to-many use case at Utah Code Camp. I'm finally getting around to it (sorry). I'm not really awesome with GitHub, so hopefully this is an acceptable place to submit this. Here it is:
My use case is an app for warehouse drivers to deliver goods to locations and receive signatures. The many-to-many comes in when we have many tickets which contain the same item. For example, pencils may be on multiple tickets, but we don't want to have pencils in the DB multiple times.
Hopefully this makes sense. I'm excited for this project, because copy/pasting a bunch of boiler plate is no fun, time consuming, hard to do right and prone to human error. I think more people would use ContentProviders if they weren't so cumbersome, and I hope Google someday writes something like the CoreData UI for building tables and relationships.