I don't know, I was speaking strictly theoretically. On Fri, Mar 27, 2009 at 10:51 PM, Jesse McGrew <[email protected]> wrote: > > Is there a limit to the number of columns a content provider can > return? I see SQLite has a default limit of 2000 columns per table, > which is more than enough, but my phony summary table wouldn't be > backed by SQLite. > > Jesse > > On Mar 27, 1:40 pm, Stoyan Damov <[email protected]> wrote: >> With 5 you can have unlimited # of columns. With 3, well, you can't. >> >> On Fri, Mar 27, 2009 at 10:35 PM, Jesse McGrew <[email protected]> wrote: >> >> > 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 -~----------~----~----~----~------~----~------~--~---
