So I get that Cursors are better with memory management than simply passing objects around. What I don't get is this:
1 - What if you are working on more complex setups than 1 table? I want 2 tables, which have a one-to-many relationship (a simple example is a Polygons table, and a Points table). How am I supposed to return a cursor that would allow access to the polygon's information, including the points? Good links welcome... 2 - Can you just wrapper stuff in simple objects? Can I create extensions of the Polygon class, perhaps DBPolygon, that call thru to the cursor? This would have low memory usage, and the rest of the app would not have to understand the database layout! What happens with crashes? I have seen some adapters around, and they seem to make all data edits directly to/from the database. Is this safe? It seems like it would be better to have objects that are manipulated, and written to the database when they are ready. If an app crashed unexpectedly after half of a row had been edited, then the database could have bad data. I would rather loose an entire row, than have a half-correct row. Any good links would be appreciated! Thanks, Ham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" 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-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
