Hi, I am using sqlit3 in my iphone application to store details of the user I have a table carrying of 50 columns. Now i have to insert data within the columns. can anybody suggest optimum way to do that which will not impact the performance.
Thanks
views:
64answers:
3
+1
A:
Best thing to do is to try whatever comes to mind, and if it's too slow, well, try something else. What have you tried? Are you experiencing performance problems?
echo
2009-11-24 05:58:24
yes, i am doing the same. but still if in case anybody else have encountered the same scenario, their thought would be helpful. experiment is going on.. :)
viswa08
2009-11-24 06:09:38
please post your results when you have them, i'm curious to know the answer. pure guess on my part, but i bet the iphone has no problem with that size table. 50 columns is pretty teensy, particularly when it comes to data inserts. now, if you have lots and lots and lots of 50 column tables, and lots and lots and lots of data in them, then joins could get interesting...
echo
2009-11-24 06:14:18
@justin: please dont scare me. i'm newbie :) fortunately..i hv only 3 table with one carrying 50+ columns and 25+ records in that table.
viswa08
2009-11-24 19:31:50
finally.. i made sequence insertion... keeping the column segerated as per the screen and update as per the edit happened to that screen.. its working ..
viswa08
2009-12-03 22:23:47
+1
A:
SQLite doesn't store empty columns, so having 50 columns will have no impact until you start putting data into them. After you insert data, it will start to take up space, but the additional cost will be minimal. What performance problems are you specifically worried about?
brianegge
2009-11-24 06:12:48
performance in terms of data retrieval from db while transition from one view to another, like it should not see visible delay to do that and this was my concern.. thanks for reply.
viswa08
2009-11-24 06:26:53
SQLite is faster than you think it is. I'd recommend trying this first, before worrying about optimizations. Odds are, your own supporting code will be much slower than the SQLite accesses.
Brad Larson
2009-11-24 13:26:34
@Brad: reason for my worry is i'm stuck with limited time to develop and i dont want to revisit the same screen because of same reason. else i would be doing all types of permutation :) and Thanks for support!
viswa08
2009-11-24 19:29:03