Advertise Mobile SDKs Books Events Forum News Social Networking Support Us
Follow @iphonedevsdk on Twitter

Mockup & CodeGen, iPhone & iPad
($9.99)

Make your own iPhone apps
and run them live!
(free)

Manu
($0.99)

Want your application or service advertised on iPhone Dev SDK?

Go Back   iPhone Dev SDK Forum

View Single Post
Old 05-21-2009, 07:19 PM   #1 (permalink)
xtr33me
Registered Member
 
Join Date: May 2009
Posts: 28
Default SQLite3 performance question

I currently have a DB with my data spread across 12 tables. Because this is my first iphone app I am unsure as to the best practices on the iphone due to memory constraints. I have 4 tabs, all of which access data from the DB. Currently my db is loaded in my appDelegate and this is where I will be writing my methods to query the DB.

My question is, is it better to populate most of the data once and let it reside in memory across the tabs or is it better to just populate certain variables when I need them, keep them resident in memory and when they flip the view release the data and populate the info for that view?

I've scoured the net and found numerous articles, but none really for a more complex setup for a db. And then ofcourse all the articles on SQL, don't need to usually worry about memory so often they will keep the object around till they don't need it anymore.

I am really using this project as a learning project, so I would prefer to know the proper way of handling this. If anyone can help or give me a good swift kick in the right direction it would be greatly appreciated. Thanks everyone!!
xtr33me is offline   Reply With Quote
 

» Advertisements
» Stats
Members: 158,842
Threads: 89,211
Posts: 380,652
Top Poster: BrianSlick (7,129)
Welcome to our newest member, immortalkenny
Powered by vBadvanced CMPS v3.1.0

All times are GMT -5. The time now is 04:16 AM.
Powered by vBulletin® Version 3.8.0
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.