[sqlite] C API reference manpages

On 31/03/16 14:39, Kristaps Dzonsons wrote: >>> Is there any interest in integrating this tool to have manpages in the >>> doc distribution without downstream bits? >> >> I think that would be cool. Integrating your tool into the source >> tree would mean that as the comment formats evolve, your

[sqlite] Calling some predefined SQL function from another custom SQL function?

> > Le 31 mars 2016 ? 13:32, Keith Medcalf a ?crit : > > > > On the third hand, this could be a case of premature optimization and > the optimal course of action is not to optimize the action before doing > it, but as Nike says, "Just Do It". > > I agree on the generic point, though here the

[sqlite] C API reference manpages

gp-signature Size: 842 bytes Desc: OpenPGP digital signature URL: <http://mailinglists.sqlite.org/cgi-bin/mailman/private/sqlite-users/attachments/20160331/79038d8e/attachment.pgp>

[sqlite] Calling some predefined SQL function from another custom SQL function?

Olivier Mascia wrote: >> Le 31 mars 2016 ? 11:03, Clemens Ladisch a ?crit : >>> I think it is obvious I could build a SQL statement from within the >>> function and execute it. But it sounds costly to involve the parser >>> (yes, it's fast) for that, isn't it? >> >> You can prepare the statement

[sqlite] Calling some predefined SQL function from another custom SQL function?

Hi, > Le 31 mars 2016 ? 11:03, Clemens Ladisch a ?crit : > >> I think it is obvious I could build a SQL statement from within the >> function and execute it. But it sounds costly to involve the parser >> (yes, it's fast) for that, isn't it? > > You can prepare the statement beforehand. Not

[sqlite] C API reference manpages

Hello, I couldn't find any way to convert the SQLite docs (via sqlite.h) to UNIX manpages, so I wrote a tool that does so: https://github.com/kristapsdz/sqlite2mdoc This generates one manpage per API reference with the proper SEE ALSO (from collected references) and IMPLEMENTATION NOTES (the

[sqlite] Calling some predefined SQL function from another custom SQL function?

While it is technically possible to convincingly fake an SQLite context to call strftimeFunc() with, it also means that you are ignoring SQLite function overloading. And making yourself dependant on internal changes to SQLite structures that are opaque for a reason. -Urspr?ngliche

[sqlite] Calling some predefined SQL function from another custom SQL function?

Olivier Mascia wrote: > Writing a scalar SQL function, is there a C-level way to call some > other scalar SQL function? The only way is to build an SQL statement from within the function and execute it. > I think it is obvious I could build a SQL statement from within the > function and execute

[sqlite] Understanding table and database locking mechanism inshared cache mode and normal mode

Hello ! You can check the behavior of sqlite3 in a multi thread environment with this program: https://gist.github.com/mingodad/79225c88f8dce0f174f5 I did it to test how fast sqlite3 can be on a system (cpu/memory/threads) and with it you can from the command line change the following

[sqlite] C API reference manpages

On 3/31/16, Kristaps Dzonsons wrote: > > Is there any interest in integrating this tool to have manpages in the > doc distribution without downstream bits? > I think that would be cool. Integrating your tool into the source tree would mean that as the comment formats evolve, your tool would

[sqlite] Note, using SQLAR compared to TGZ archive

Thanks Richard, I first saw a reference from the mailing list back in May 2014. I've been reading the list since April 2010. I'm not much of a C programmer, but I will let you know. I'm working on adding "comments" or tags to accompany the filenames. For example, the file

[sqlite] Calling some predefined SQL function from another custom SQL function?

On Thu, Mar 31, 2016 at 6:39 AM, Olivier Mascia wrote: > > Le 31 mars 2016 ? 11:03, Clemens Ladisch a ?crit : > >> I think it is obvious I could build a SQL statement from within the > >> function and execute it. But it sounds costly to involve the parser > >> (yes, it's fast) for that, isn't

[sqlite] Calling some predefined SQL function from another custom SQL function?

On the third hand, this could be a case of premature optimization and the optimal course of action is not to optimize the action before doing it, but as Nike says, "Just Do It". > -Original Message- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > bounces

[sqlite] Understanding table and database locking mechanism in shared cache mode and normal mode

On 31 Mar 2016, at 12:06am, Srikanth Bemineni wrote: > > In this case a new connection is > being given to a thread in shared cache mode to the database. If one of the > thread gets a SQLITE_LOCKED status for statement execution, we use try > again after some time assuming the other thread

[sqlite] Understanding table and database locking mechanism in shared cache mode and normal mode

Hi In shared cache mode the locking seems to be per table level basis. Which seems to not block my operations on the other tables in the same database. When there are multiple connections, any transaction is going to create a data base level lock, which may result in many write as well as read

[sqlite] Understanding table and database locking mechanism in shared cache mode and normal mode

Hi, if( (lastStatus == SQLITE_OK) && mystatement) { m_lastStatus = sqlite3_step(mp_statement); while( lastStatus == SQLITE_LOCKED || lastStatus == SQLITE_BUSY) { sleep(randomtime) lastStatus = sqlite3_step(mp_statement); } } My common