Hi,

currently I am not creating large subqueries or views and therefore storing the 
temporary data in memory is a solution but I would like to have a future proof 
solution. And I do not like to think about it anymore in the future.

Or can we stop deprecating sqlite3_temp_directory? Why was it at all 
deprecated? It seems to be (according to the comments) that there has been some 
trouble with assigning and releasing the variable but this can be overcome by 
not exposing it publicly and using an appropriate function instead.

Regards,
Hartwig

> Am 2018-06-09 um 19:16 schrieb Dan Kennedy <danielk1...@gmail.com>:
> 
> On 06/10/2018 12:00 AM, skywind mailing lists wrote:
>> Hi,
>> 
>> what is your experience with temporary files requested by SQLite3 on 
>> Android? I am using SQLite3 natively on Android - I compiled SQLite3 by 
>> myself - and get an error when SQLite3 tries to create temporary files 
>> because:
>> 
>> - the directories
>>      /var/tmp
>>      /usr/tmp
>>      /tmp
>>      .
>>   are not accessible by a standard user (and therefore the app);
>> - getenv is not guaranteed to be supported (or?);
>> - sqlite3_temp_directory should not be used because it is deprecated.
>> 
>> What are you doing?
> 
> People usually end up building with:
> 
>   -DSQLITE_TEMP_STORE=3
> 
> This causes SQLite to use main memory for all temp files.
> 
> Dan.
> 
> 
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> 

_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to