On Mar 27, 7:43 am, Stoyan Damov <[email protected]> wrote: > Possible Approach 5, similar to 3 - a phony table with 3 columns: > > 1. Name/Key/Whatever > 2. Type ("enumeration") > 3. Data (string) > > The client would only need to convert the data from string to the > appropriate type.
Hmm. I'm not sure what the benefit of this is over #3. This basically turns the result set on end, requiring extra complexity in the client (looping over rows) without simplifying the server implementation. It does get rid of the "single row" objection, I suppose. Come to think of it, if that's my only objection to #3, maybe the answer is clear... Jesse --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
