Hi Ryan, Do you mean it would be more efficient to generate entries such as these (with randomly chosen integers and running numbers) in the application and then committing them to the database with sqlite3_exec or similar?
For a large number of entries, I assumed there would be greater overhead in preparing and binding the values than both generating and storing them with a single RCTE. On 8 January 2018 at 10:23, R Smith <ryansmit...@gmail.com> wrote: > > On 2018/01/08 11:17 AM, Shane Dev wrote: > >> >> P.S one reason I am using SQL instead the main application to perform such >> calculations is precisely to avoid using variables (and hence the evils of >> mutable state). Why do you say it is more efficient? >> > > Because it is much more efficient, memory used in stead of computations > through the DB engine. It's even vastly more efficient when you do these > things in your programming language (Zero parsing to start with)... > > That however doesn't mean you should only do it this way. There are > obviously merits (such as mutable state evility, if there is such a word) > to using a less efficient method. > > _______________________________________________ > sqlite-users mailing list > email@example.com > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list firstname.lastname@example.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users