I certainly wouldn't recommend grabbing the entire contents of the table and shoving that into the view. Instead what you could do is override the AutoCompleteTextView's PerformFiltering() method and run your query based on the actual search term instead of selecting everything.
On Tue, Oct 18, 2011 at 8:14 AM, bmellac <bmel...@nomadvantage.com> wrote: > You also mentioned not knowing how to call into a base class constructor > from > the deriving class. In my sample code you posted, you can see I'm doing > that > in my helper class: > > public NoteDatabaseHelper(Context context) > : base(context, DATABASE_NAME, null, DATABASE_VERSION) > > Sometime I surprise myself... not seeing this line of code... thx for > pointing it :) > > > so if I follow you, the object DAL could be a solution, but in my simple > exemple, I have a client table wich containts 100000 records. > I want a autocompletetextview able to "search" into that table. > If I were using a DAL providing a list of client objects, I would have to > instanciate 100.000 objects wouldn't I ? > And would consume way too much memory no ? > As a matter of fact, my first sample was using an arrayadapter, populating > a > List<string> from the database... I end up having JNI exeptions for too > many > instanciations.... > > > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/Mono-Data-Sqlite-and-cursors-tp4913036p4913442.html > Sent from the Mono for Android mailing list archive at Nabble.com. > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid >
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
