Re: [sqlite] New word to replace "serverless"
On 2020-01-28 00:19, Richard Hipp wrote: > daemon-less? This is my favorite, the only problem is that it is culturally more a Unix-y term. But there are plenty of other good suggestions from this thread. - embedded - self-contained - in-process - integrated - connectionless Also take into consideration, to quote Warren Young: ``Keep using the term. We were here first.'' -- Kind Regards, Jan ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Regarding CoC
On 2018-10-24 13:42, Dominique Devienne wrote: > On Wed, Oct 24, 2018 at 1:10 PM Wout Mertens wrote: >> [...] write the rules in Ye Olde English. [..] > > He was "Italian", and more likely to write in Latin, not English, old or > new. > The SQLite doc is English only because that's DRH native tong (I assume). Minor point, but I don't think the English translation is used merely because of drh's native tongue; it also happens to be a good choice to use English on the Internet so as many people as possible can read it. > Lets not pretend the rules are from English origin please. --DD I don't think that was what Wout meant. Read "Ye Olde English" as "Aesthetically 'old'", not "use the original". Point was merely to give some visual clues to the reader that "the original is very old", since it's clear a lot of people aren't reading the first part of the document. And again, English is a good choice to reach as many as possible. -- Kind Regards, Jan ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] reset after failed step
Hello,
Is this (conceptually) correct:
-
.. bind arguments ..
sqlrc = sqlite3_step(stmt);
if(sqlrc == SQLITE_ROW || sqlrc == SQLITE_DONE) {
sqlrc = sqlite3_reset(stmt);
assert(sqlrc == SQLITE_OK);
}
.. bind other arguments ..
sqlrc = sqlite3_step(stmt);
if(sqlrc == SQLITE_ROW || sqlrc == SQLITE_DONE) {
sqlrc = sqlite3_reset(stmt);
assert(sqlrc == SQLITE_OK);
}
sqlrc = sqlite3_finalize(stmt);
assert(sqlrc == SQLITE_OK);
-
I.e. reset should only be run on ROW and DONE. On step error, the
statement's state is reset implicitly by sqlite3_step()?
--
Kind regards,
Jan Danielsson
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] bounded id
Hello, I have a wire-protocol which uses an uint32_t to identify transfers, and each of the transfers is represented by a row in a table in an sqlite database. I can't make the rowid a uint32_t, but that's essentially the behavior I'm looking for -- I'd like to be able to insert a new row into the table, then ask for the last inserted row id and use that identifier in the wire-protocol. Are there any good options to accomplish this [limit the auto-assigned identifier]? The obvious solution is to record-keep identifiers outside of the database, but the sqlite database is responsible for assigning other other identifiers; it would be nice not to break that abstraction if possible. -- Kind regards, Jan Danielsson ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
