Hello Jang, Monday, December 10, 2007, 1:39:02 AM, you wrote:
JJ> Hello, JJ> JJ> Now I'm using SQLite v3.4.2 in my Mobile Device(ARM9-200Mhz, 8MB SRAM) JJ> and it works fine. JJ> JJ> But when I updated to SQLitev3.5.3 this time I am facing problem. JJ> JJ> Please let me know why it is happening. JJ> JJ> This is my test source in MS's VisualC++ 6.0 (Console application). JJ> JJ> http://cfs7.blog.daum.net/upload_control/download.blog?fhandle=MElCMXRAZ JJ> nM3LmJsb2cuZGF1bS5uZXQ6L0lNQUdFLzAvMC56aXA=&filename=0.zip&filename=SQL3 JJ> 53_VC6.zip JJ> Problem 1. JJ> when I use "mem1.c" and use "Order By", it require more memory than I JJ> expected. JJ> It seems has same problem when I use "mem3.c". I want use less than 1MB. JJ> So I set "SQLITE_DEFAULT_CACHE_SIZE=800" and JJ> "SQLITE_DEFAULT_TEMP_CACHE_SIZE=200". JJ> JJ> Problem 2. JJ> When I use "mem3.c" and set "SQLITE_MEMORY_SIZE = 1024000", "insert" was JJ> failed. JJ> JJ> Please help am I setting ANY WRONG PARAMETERS. JJ> JJ> Best Regards, JJ> Jang JJ> I've run into the same problem. Mem3.c doesn't fail very gracefully. SQL just stops working with an out of memory error when you're out and I haven't figured a good way to estimate how much memory I might need. It would be nice if you could set some high water mark but, still exceed it when needed and the pool coult free up whatever memory exceeds the water mark. On the flip side, when it's working it's exceptionally fast. -- Best regards, Teg mailto:[EMAIL PROTECTED] ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------