Re: [sqlite] Fw: Database is locked exceptions

arameters which don't exist > in SQLite, and I don't know enough about how it works. Perhaps somebody > else has a suggestion. Or perhaps you can contact the authors of that web > page and ask them. > > > Simon. > _______

Re: [sqlite] Locking errors on network

;) > > Regards and best wishes, > > Justin Clift > > > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Scott Robison ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Locking errors on network

ked use. Of course, it would no longer be a zero configuration completely embedded system, but it would be a fairly minimal shim. Of course, it would itself require debugging, so it's not like it would be a magical solution. Still, if the SQLite "service&

Re: [sqlite] Bug report: USBAN failure

On Dec 3, 2014 12:57 AM, "Clemens Ladisch" wrote: > > James K. Lowden wrote: > > /* Copy N bytes of SRC to DEST. */ > > extern void *memcpy (void *__restrict __dest, > > __const void *__restrict __src, size_t __n) > > __THROW __nonnull ((1, 2)); > >

Re: [sqlite] Bug report: USBAN failure

On Dec 3, 2014 12:57 AM, "Clemens Ladisch" wrote: > > Do you have a standard that allows NULL? The one I quoted does not. Note: I'll have to double check my copy of the C90 standard document, but my re-reading of the C99 quote leads me to the conclusion that NULL is a valid

Re: [sqlite] Bug report: USBAN failure

On Wed, Dec 3, 2014 at 2:17 AM, Clemens Ladisch <clem...@ladisch.de> wrote: > Scott Robison wrote: > > On Dec 3, 2014 12:57 AM, "Clemens Ladisch" <clem...@ladisch.de> wrote: > >> Do you have a standard that allows NULL? The one I quoted does not. > &g

Re: [sqlite] Bug report: USBAN failure

On Wed, Dec 3, 2014 at 9:50 AM, Stephan Beal <sgb...@googlemail.com> wrote: > On Wed, Dec 3, 2014 at 5:35 PM, Scott Robison <sc...@casaderobison.com> > wrote: > > > standards have all been ISO standards. Pedantic? Yes. Obviously DRH is > > willing to ma

Re: [sqlite] Bug report: USBAN failure

first > standard Clemens quoted. > That is the C99 standard. C90 did not have that restriction. A lot of projects target C90 for maximum portability. In this particular case it does not make SQLite incompatible with C90 to accommodate C99, so it has been accommodated. Still, I would maintain

Re: [sqlite] [SQLite]Ba​sic query

On Dec 8, 2014 2:10 AM, "Shinichiro Yoshioka" wrote: > > Hi, > > I'm about to use sqlite-amalgamation(sqlite3.c) on Visual C++. > But although the compiling was successfully finished, even if I set break > point > on the source code, I can't trace the working line in

[sqlite] sqlar

, and if successful, loops on readdir. But it never calls closedir. In my scenario, it would fail after processing 198 files. I'm sure that number is dependent on how many directories, and I never thought to track that, and I'm sure it's probably platform defined anyway. Just an FYI. -- Scott Robison

Re: [sqlite] sqlar

On Wed, Dec 10, 2014 at 3:07 PM, Richard Hipp <d...@sqlite.org> wrote: > On Wed, Dec 10, 2014 at 4:58 PM, Scott Robison <sc...@casaderobison.com> > wrote: > > > In the function add_file it checks if a filename is a directory. If so, > it > > calls opendir,

Re: [sqlite] Encrypted database

gt; The exact algorithm and key strength selected probably depends on the > > version of Windows being used. > > > > -- > > Joe Mistachkin > > > > -- >-- > -- > --Ô¿Ô-- > K e V i N > __

Re: [sqlite] Encrypted database

Apologies for the noise from the empty reply. They shouldn't put "send" & "expand quote" buttons so close together. On Sun, Dec 14, 2014 at 4:40 AM, Mujtaba Ali Panjwani wrote: > Well, I have tried various applications like Navicat premium, SQlite > sorcerer, sqlite

Re: [sqlite] using a hex integer as input to DateTime

ame as 0x1234ABCD (sans quotes). -- Scott Robison ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] LIKE vs GLOB vs MATCH vs REGEXP

r a reason in SQL code to choose the function form of the LIKE (or other) operator over the operator itself. Is it intended that the operator form of the expression will always behave exactly like the function form of the expression (with the appropriate reordering of argument

Re: [sqlite] Inserting/removing large number of rows with index

On Fri, Jan 16, 2015 at 3:47 AM, Hick Gunter wrote: > It depends in how you define "update the index". > > If you mean "write to disk" then this happens "once, at the end of the > transaction" (the exact process differs depending on the journal mode). > > If you mean "change

Re: [sqlite] LIKE vs GLOB vs MATCH vs REGEXP

On Fri, Jan 16, 2015 at 5:23 AM, Jay Kreibich <j...@kreibi.ch> wrote: > > On Jan 16, 2015, at 5:06 AM, Scott Robison <sc...@casaderobison.com> > wrote: > > > LIKE & GLOB can be overridden with user defined functions. According to > > https://www.sqlite.org

Re: [sqlite] LIKE vs GLOB vs MATCH vs REGEXP

On Fri, Jan 16, 2015 at 5:56 AM, Richard Hipp <d...@sqlite.org> wrote: > On 1/16/15, Scott Robison <sc...@casaderobison.com> wrote: > > LIKE & GLOB can be overridden with user defined functions. According to > > https://www.sqlite.org/lang_corefunc.html LIKE can be

Re: [sqlite] LIKE vs GLOB vs MATCH vs REGEXP

On Jan 16, 2015 8:05 AM, "Simon Slavin" wrote: > > > On 16 Jan 2015, at 12:23pm, Jay Kreibich wrote: > > > They can all be (re)defined, some just happen to have default functions: > > > > https://www.sqlite.org/lang_expr.html#like > > Might be worth noting

Re: [sqlite] sqlite3 tool bug

aid as much IIUC) go back in time and make changes that were set in stone years ago, but he specifically does not do it to maintain backward compatibility. Heck, if nothing else, I'm sure he'd love to go back and eliminate every bug that has forced a patch update. -- Scott Robison ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] sqlite3 tool bug

On Jan 17, 2015 7:29 PM, "Dave Dyer" > Here in the real world, when everything is working, we ask "why upgrade". But it wasn't working correctly so the statement doesn't really answer the question asked. :) ___ sqlite-users

Re: [sqlite] Invalid column prefix returned in SELECT with joined subquery

On Jan 25, 2015 7:28 PM, "Simon Slavin" wrote: > > > While you're discussing possibilties and alternatives, what should be returned as the name for the following column > > SELECT 1*2 FROM myTable There are a few possibilities: "1*2" "2" "two" "bob" Or any case

Re: [sqlite] Truncation of floating point numbers in SQLite?

On Mon, Feb 2, 2015 at 8:08 PM, Donald Shepherd wrote: > sqlite3_bind_double calls sqlite3VdbeMemSetDouble which has a specific > check against NaN. My assumption is that this is what results in NaNs not > round tripping and instead coming back out as SQLITE_NULL: > >

Re: [sqlite] binding multiple values in a query

On Feb 12, 2015 1:26 AM, "Dominique Devienne" wrote: > > We fill the collection client-side, bind it, execute that 1 statement, and > get back many rows, all in a single round-trip to the server (thanks to > prefetching on the select side). Mind you, this is not nearly as

Re: [sqlite] Messages posted on Nabble not getting to list

On Fri, May 27, 2016 at 4:43 AM, Jonathan Moules < jonathan-li...@lightpear.com> wrote: > I think there are two different use cases for a mailing list such as this, > and they're each better served by different access method; either email or > forums. > > One use case is the individual with a

Re: [sqlite] Messages posted on Nabble not getting to list

On Fri, May 27, 2016 at 2:10 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 27 May 2016, at 7:50pm, Scott Robison <sc...@casaderobison.com> wrote: > > > I'd like to see some sort of hybridized approach myself (for my own > > projects, not advocating for SQ

Re: [sqlite] Messages posted on Nabble not getting to list

start using it. Good points. Of course, will billions of deployments around the world, SQLite isn't hurting for devs or users (whether they know they're using SQLite or not). :) -- Scott Robison ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Segfault during FTS index creation from huge data

On Tue, Apr 28, 2015 at 7:08 AM, Hick Gunter wrote: > Getting "NoMem" sounds very much like a memory leak somewhere, with the > most likely place being your own application, followed by the wrapper you > are using, the FTS code and lastly the SQLite core. Lastly because the > SQLite core is

[sqlite] Segfault during FTS index creation from huge data

On Tue, Apr 28, 2015 at 1:03 PM, Dan Kennedy wrote: > On 04/29/2015 01:55 AM, Scott Robison wrote: > >> I just took a quick glance at the FTS code. As I said, it has been a >> couple >> years, but this looks like the malloc that was failing for me at the time: >>

[sqlite] Segfault during FTS index creation from huge data

passed to > sqlite3_malloc() causing the OOM report. Huh. In looking at the code some more, it could have been in segment merging code in fts3_write.c @ http://www.sqlite.org/cgi/src/artifact/4f005f78592a1447 ... I'll try to generate some test data and see if I can get you some real information vs hazy recollections. -- Scott Robison

[sqlite] Segfault during FTS index creation from huge data

tyle system. It was strictly Windows. -- Scott Robison

[sqlite] Segfault during FTS index creation from huge data

On Tue, Apr 28, 2015 at 5:06 PM, Simon Slavin wrote: > > On 28 Apr 2015, at 11:49pm, Scott Robison wrote: > > > I never saw a segfault in my case, though I never tried anything on any > > posix style system. It was strictly Windows. > > Windows doesn't call i

[sqlite] Segfault during FTS index creation from huge data

Win 7 64 bit system, building & testing 32 & 64 bit versions of our app. On Apr 29, 2015 1:34 AM, "Eduardo Morras" wrote: > On Tue, 28 Apr 2015 16:49:46 -0600 > Scott Robison wrote: > > > On Tue, Apr 28, 2015 at 4:27 PM, Artem wrote: > >

[sqlite] Segfault during FTS index creation from huge data

Personally I don't see it as a bug. A limitation, yes. A different algorithm that requires less ram would remove / change the limit. I'll be trying some sample data tomorrow (if time permits) to see if I can come up with any ideas. I described an approach in a previous email where I divided my

[sqlite] Segfault during FTS index creation from huge data

locking, I don't think Sqlite is responsible when malloc lies about what should be considered a failed memory allocation which should return null. On Apr 29, 2015 2:28 AM, "Simon Slavin" wrote: > > On 29 Apr 2015, at 9:21am, Scott Robison wrote: > > > Personally I don't see

[sqlite] Segfault during FTS index creation from huge data

I created multiple FTS virtual tables and inserted data into specific tables based on ID. The FTS tables used the content option to specify the text was stored elsewhere. Something like "insert into FTSBUCKET# (...) ..." where # was computed from a rowid to spread the load around. This may not be

[sqlite] Segfault during FTS index creation from huge data

On Apr 29, 2015 2:55 AM, "Dan Kennedy" wrote: > > On 04/29/2015 03:39 PM, Scott Robison wrote: >> >> On windows, malloc returns null if the allocation fails. Sqlite detects >> this and returns an error. >> >> On linux, malloc may return a non

[sqlite] Segfault during FTS index creation from huge data

", nullptr, nullptr, nullptr)); chk(sqlite3_close(db)); } catch (const std::string& x) { std::cout << std::endl << std::endl; std::cout << "caught exception: " << x << std::endl; std::cout << "ull = " << ull << std::endl; } while (!allocs.empty()) { delete [] allocs.back(); allocs.pop_back(); } return 0; } -- Scott Robison

[sqlite] Segfault during FTS index creation from huge data

On Wed, Apr 29, 2015 at 8:04 PM, James K. Lowden wrote: > On Wed, 29 Apr 2015 02:39:50 -0600 > Scott Robison wrote: > > > On linux, malloc may return a non null yet invalid pointer and only > > fail when the memory is accessed because it wasn't really available. > >

[sqlite] Segfault during FTS index creation from huge data

On Wed, Apr 29, 2015 at 8:23 PM, Scott Robison wrote: > > 1. From http://linux.die.net/man/3/malloc > > By default, Linux follows an optimistic memory allocation strategy. This >> means that when *malloc*() returns non-NULL there is no guarantee that >> the memory real

[sqlite] Segfault during FTS index creation from huge data

On Apr 29, 2015 11:50 PM, "Dan Kennedy" wrote: > > On 04/30/2015 07:41 AM, Scott Robison wrote: >> >> >> I wrote up some test code today that definitely forces a SQLITE_NOMEM >> condition, and there are no leaks (though there are a couple really large >

[sqlite] Segfault during FTS index creation from huge data

On Thu, Apr 30, 2015 at 11:42 AM, James K. Lowden wrote: > On Wed, 29 Apr 2015 20:29:07 -0600 > Scott Robison wrote: > > > > That code can fail on a system configured to overcommit memory. By > > > that standard, the pointer is invalid. > > > > > &

[sqlite] Compile warnings

I suspect this is similar to another "recent" discussion about passing null pointers to mem* library functions. C89 allowed zero or null. C99 seems to forbid it. I'm going from memory here, can look at standards later if desired On Aug 20, 2015 8:08 AM, "Richard Hipp" wrote: > On 8/20/15,

[sqlite] Compile warnings

ating as many warnings as possible, but it is a lot harder to be 100% warning free in portable source like SQLite. -- Scott Robison

[sqlite] Compile warnings

the warning. > > Cheers, > Bernhard > > 2015-08-20 17:56 GMT+02:00 Scott Robison : > > > On Thu, Aug 20, 2015 at 9:35 AM, Bernhard Schommer < > > bernhardschommer at gmail.com> wrote: > > > > > It's not a bug. It actually comes from the warni

[sqlite] Compile warnings

ust be ignored in this case, just as I ignore warnings that are generated by Visual C++ when I compile SQLite there. -- Scott Robison

[sqlite] design problem involving trigger

Another consideration: it is possible that two different anonymous books are indeed different books. It is also possible a given "author" releases a new rewritten book with the same name. I'm thinking of the Hardy Boys series in particular from my personal experience. Not a big deal, but thought

[sqlite] Compile warnings

itimate > choices. Modifying the code to suppress the warning is NOT. > > Regards > David M Bennett FACS > > Andl - A New Database Language - andl.org > > -Original Message- > From: sqlite-users-bounces at mailinglists.sqlite.org > [mailto:sqlite-users-bounces

[sqlite] Compile warnings

andl.org > > -Original Message- > From: sqlite-users-bounces at mailinglists.sqlite.org > [mailto:sqlite-users-bounces at mailinglists.sqlite.org] On Behalf Of Scott > Robison > Sent: Saturday, 22 August 2015 2:05 AM > To: General Discussion of SQLite Database > ; davi

[sqlite] Compile warnings

On Sat, Aug 22, 2015 at 10:31 AM, Richard Hipp wrote: > On 8/22/15, Scott Robison wrote: > > I don't object to a change to accommodate C99 null > > pointer requirements > > Please note that the warning in question has nothing to do with NULL > pointers. The pointer p

[sqlite] Compile warnings

one universal right solution to this issue". The only thing I can say is: not all warnings are equally bad, and I will review warnings that are generated from third party code (such as SQLite) but I rarely will do anything to try to suppress them. Making my code right is a hard enough task. I don't need to "fix" third party code (as long as it passes testing). -- Scott Robison

[sqlite] Compile warnings

ers-bounces at mailinglists.sqlite.org > [mailto:sqlite-users-bounces at mailinglists.sqlite.org] On Behalf Of Scott > Robison > Sent: Monday, 24 August 2015 8:25 AM > To: davidb at pfxcorp.com; General Discussion of SQLite Database > > Subject: Re: [sqlite] Compile warn

[sqlite] Compile warnings

gt; David M Bennett FACS > > *Andl - A New Database Language - andl.org <http://andl.org>* > > > > > > *From:* Scott Robison [mailto:scott at casaderobison.com] > *Sent:* Tuesday, 25 August 2015 1:24 AM > *To:* General Discussion of SQLite Database < &g

[sqlite] Performance problems on windows

On Aug 25, 2015 5:21 AM, "Jakub Zakrzewski" wrote: > > Hi, > > The slowdown is confirmed by one of our customers. He uses Win 2008 Server x64. I'm testing on Win7 x64. This might be obvious in which case my apologies for bringing it up but: are these systems demonstrating slowness perhaps

[sqlite] Why sqlite show qualified column names when selecting from views ?

On Aug 25, 2015 1:02 PM, "Petite Abeille" wrote: > > > > On Aug 25, 2015, at 8:53 PM, R.Smith wrote: > > > > I vote to change it every release... Stimulate better habits! > > Seconded. Keep them on their toes! > Or randomly generate names after every prepare! Or just leave them anonymous.

[sqlite] order by not working in combination with random()

ion in some way to make it clear random behaves this way (and perhaps that column aliases in an order by clause re-evaluate their definitions from the select). But my vote doesn't mean much, so whatever. Maybe the best answer to this issue is "to change the functionality at this point may break existing queries that depend on the current behavior" and thus it should not be changed. -- Scott Robison

[sqlite] order by not working in combination with random()

! > Are you saying ambiguous column is what *should* be reported, or are you saying that is the error message that *is* reported? Because I just tried the query with sqlite3.exe 3.8.11 and it worked just fine. > > > > Thu Aug 27 2015 6:48:54 pm CEST CEST from "Scott Robison"

[sqlite] order by not working in combination with random()

as MySQL 5.6. SQLite: we already know. I think it still comes back to my earlier comment: Would changing it to behave more like the most common / expected outcome above be a breaking change? -- Scott Robison

[sqlite] order by not working in combination with random()

4402 sys 0.00 sqlite> Note: I pasted the first query that begins drop table, then used up arrow and edited the 1000 to 10 for the second query. Further, I didn't have time to try a full billion, so I settled for 10 million. Also used a transient in-memory database. Finally, I am using Windows 7 Professional on a box with 16 GiB of RAM. Do you see the same behavior for a test of 10M rows (that the second line takes the same amount of time as the first)? -- Scott Robison

[sqlite] website documentation wording

/listinfo/sqlite-users >> >> >> > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- Scott Robison

[sqlite] sqlite3_errmsg and wide char

all through history. They might not have been called "code pages" but Mac most definitely had different character sets to support different markets. -- Scott Robison

[sqlite] Problem with accumulating decimal values

hive.com/sqlite-users at > mailinglists.sqlite.org/msg04587.html > (web search sqlite "simple math question") > > It has background, theory, and they show how the conversions of > decimals to floating point and how they add works, using several > examples. > +1 -- Scott Robison

[sqlite] Bug with DATETIME('localtime')

y. That functionality would almost certainly only be required for hosted implementations. Freestanding implementations have a much smaller set of requirements (they don't even require the *current* time functions!), and are the types of implementations used in targeting all these embedded devices that make SQLite (likely) the most deployed software in the world. -- Scott Robison

[sqlite] Bug with DATETIME('localtime')

ee on what 100% accurate really means). We need a metric calendar. I propose redefining the second so that a day is 100,000 seconds long... ;) -- Scott Robison

[sqlite] about attach database

ase. I say no advantage ... maybe I just can't think of one. Why do you think there would be an advantage to deferring the open & schema processing of an attached database? -- Scott Robison

[sqlite] about attach database

On Wed, Dec 16, 2015 at 1:37 AM, Dominique Pell? wrote: > Scott Robison wrote: > > > Why would that be of benefit to you? Are you intending to attach a > database > > and never use it? It seems to me the same amount of time will be taken > > either way. >

[sqlite] batch or one by one?

dware, your operating system ... who knows what. -- Scott Robison

[sqlite] Suggestions for Fast Set Logic?

While I am opposed to premature optimization as well, this is not clearly a case of that. As described, the user will be able to create arbitrarily complex queries. Since it is impossible to know in advance what indexes might be required, breaking it down to individual sub queries with simple

[sqlite] Suggestions for Fast Set Logic?

On Jul 11, 2015 6:16 PM, "James K. Lowden" wrote: > > On Fri, 10 Jul 2015 09:54:27 -0600 > Scott Robison wrote: > > > As described, the user will be able to create arbitrarily > > complex queries. Since it is impossible to know in advance what > > ind

[sqlite] Suggestions for Fast Set Logic?

On Jul 11, 2015 7:11 PM, "Simon Slavin" wrote: > > > On 12 Jul 2015, at 2:02am, Scott Robison wrote: > > > I'm just saying that knowing which index to create in advance is impossible > > if the user can specify arbitrarily complex where clauses. > > You

[sqlite] Suggestions for Fast Set Logic?

On Sun, Jul 12, 2015 at 9:46 AM, James K. Lowden wrote: > On Sat, 11 Jul 2015 19:02:59 -0600 > Scott Robison wrote: > > > > I don't follow you. A complex query is an assemblage of clauses. > > > Whether or not broken down "to individual sub queries", th

[sqlite] Query takes 8 seconds on one machine but I abort after 40+ minutes on other machines

ans of copying the file didn't result in CRLF translation of some sort. Still, if the copy process did modify the file in some way, I suspect the problem would have been a corrupt file error, not a slow running query. -- Scott Robison

[sqlite] User-defined types

On Thu, Jun 4, 2015 at 4:21 PM, Darko Volaric wrote: > I'm saying that SQL is alien to the platform it's being used on and native > is better. I'm trying to make a general point (in vain it seems), I don't > use JSON. > {bunch of stuff snipped} I understand where you're coming from, I think. I

[sqlite] User-defined types

On Fri, Jun 5, 2015 at 11:07 AM, Stephen Chrzanowski wrote: > First, who said that you had to keep all 6 sets of languages in your head > at once? I've never been told that, and I've been doing software > development since I was 8, taken several training courses in elementary, > high school,

[sqlite] Mozilla wiki 'avoid SQLite'

On Jun 14, 2015 9:43 AM, "Stephen Chrzanowski" wrote: > > Most of that looks to be more like common sense things rather than SQLite > specific, so why they're calling out SQLite, I've no idea. Also, this doc > was last modified more than a year ago. Stuff has changed both within FF > as well as

[sqlite] Mozilla wiki 'avoid SQLite'

sers > > _______ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- Scott Robison

[sqlite] Mozilla wiki 'avoid SQLite'

e.org [mailto: > sqlite-users-bounces at mailinglists.sqlite.org] On Behalf Of Alex Bowden > Sent: Monday, June 15, 2015 11:00 AM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Mozilla wiki 'avoid SQLite' > > > > On 15 Jun 2015, at 15:44, Scott Robison wrote: > > &g

[sqlite] problem compiling std_call dll

X version of the symbol might be in the obj file (the source file got stdcall right), while consumers using the header try to use the cdecl form without the @X (because the prototype is different in the two locations. I hope this isn't too rambling. Just thoughts from a sleep deprived person. :) -- Scott Robison

[sqlite] problem compiling std_call dll

ion. See https://en.wikipedia.org/wiki/X86_calling_conventions#stdcall ... In any case, the @X doesn't *need* to be part of the symbol (the Windows API entry points don't use it, even though they use stdcall as I understand it) as the cleanup code isn't dependent on the symbol. It's just a convention. -- Scott Robison

[sqlite] problem compiling std_call dll

fault convention used by (at least) Microsoft compilers when using the stdcall calling convention. It's a confusing bit of terminology what with multiple applications of the word "convention" so I just wanted to clarify what I meant. I understand Windows does not require everyone to use stdcall for their own APIs and such. -- Scott Robison

[sqlite] update of view via trigger

the original trigger would behave. Finally, my question: Is there some sort of syntax that I'm missing that would "simplify" my schema with a single update trigger, or is this the proper way to "update" individual columns of a view? -- Scott Robison

[sqlite] update of view via trigger

On Mar 6, 2015 7:33 AM, "Igor Tandetnik" wrote: A bunch of good stuff snipped... Thanks for the alternative suggestions. In thinking it over since my message, I've decided the multiple trigger approach isn't at all bad. A little verbose, but each column of the view has its own callback and

[sqlite] C++ ORM

of reflection in C++ might lead to a less manageable ORM. Still, never hurts to ask. -- Scott Robison

[sqlite] Query times vary between 0.2 s and 30 s for very

On Mar 21, 2015 1:43 PM, "James K. Lowden" wrote: > > The query optimizer has to be sophisticated enough to recognize > those conditions, which is unlikely in the case of a temporary table. Are temporary tables really that different? Other than being dropped automatically at the end of a

[sqlite] Query times vary between 0.2 s and 30 s for very

On Mar 21, 2015 1:43 PM, "James K. Lowden" wrote: > > The query optimizer has to be sophisticated enough to recognize > those conditions, which is unlikely in the case of a temporary table. Are temporary tables really that different? Other than being dropped automatically at the end of a

[sqlite] Query times vary between 0.2 s and 30 s for very

On Sun, Mar 22, 2015 at 2:47 PM, James K. Lowden wrote: > On Sat, 21 Mar 2015 14:36:47 -0600 > Scott Robison wrote: > > > > > > > The query optimizer has to be sophisticated enough to recognize > > > those conditions, which is unlikely in

[sqlite] What is wrong with this simple SQL?

ion, and I didn't expect the "namespace pollution" (which isn't really namespace pollution, but that's how it seemed at the time). -- Scott Robison

[sqlite] What is wrong with this simple SQL?

On Sun, Mar 22, 2015 at 5:02 PM, Igor Tandetnik wrote: > On 3/22/2015 6:52 PM, Scott Robison wrote: > >> Thinking back to when I was first learning SQL, I remember being surprised >> in a similar way. To my procedural / object oriented / imperative way of >> thinking

[sqlite] Multiple instances of the same program accessing the same db file

If I missed something and this is all old hat, my apolgoies for the repetition. -- Scott Robison

[sqlite] What software is deployed more than SQLite?

g library used everywhere, or are there competing > implementations? > Obviously this is just guess work, but I would tend to give the edge to SQLite for one reason: It is statically linked into so many programs by design, whereas the others are (arguably) more often dynamically linked / shared objects. -- Scott Robison

[sqlite] Segfault during FTS index creation from huge data

One, you should remove sqlite-users at sqlite.org from your To list. I keep bouncing email when I reply to you. Not a big deal, just an FYI. Two: On Sun, May 3, 2015 at 2:13 PM, James K. Lowden wrote: > On Thu, 30 Apr 2015 12:47:57 -0600 > Scott Robison wrote: > > > Perhaps

[sqlite] saving :memory:database to disk

database to another. See http://sqlite.org/backup.html for details. -- Scott Robison

[sqlite] AUTOINC vs. UUIDs

th the originally linked article that integer primary keys should almost always be avoided, and there was a lot of exaggerating in the risks involved. Still, UUIDs (or other similarly long or longer hash or quality random number source based IDs) can be an effective technique when used appropriately. -- Scott Robison

[sqlite] AUTOINC vs. UUIDs

able to merge or update data from multiple distributed databases into a master. > > > -Original Message- > > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > > bounces at mailinglists.sqlite.org] On Behalf Of Scott Robison > > Sent: Wednes

[sqlite] AUTOINC vs. UUIDs

can do the same sort of thing with 64 bit integers (as described above by SQLite), or 256 bit blobs. Heck, one can do it with one bit integers, though the chance of collision is rather high. :) -- Scott Robison

Re: [sqlite] Concrete example of corruption

Might there be a way to implement a custom VFS for Mac to deal with this? On Thu, Dec 5, 2013 at 3:55 PM, William Garrison <1billgarri...@gmail.com>wrote: > On Thursday, December 5, 2013, L. Wood wrote: > > > A fact of reality: Documents can be moved by the program's users. > > > > The database

Re: [sqlite] Concrete example of corruption

t; > On 6 Dec 2013, at 12:00am, Scott Robison <sc...@casaderobison.com> wrote: > > > Might there be a way to implement a custom VFS for Mac to deal with this? > > One problem is that to be able to call fsevents you have to link in a huge > amount of the standard Mac su

Re: [sqlite] Recursive query?

> That's great news! This will be a serious step up in feature set for SQLite, both in ease of use and power, I look forward to it. -- Darren Duncan It will be available in the SQLite Gold edition for $10,000. {jk} ___ sqlite-users mailing list

Re: [sqlite] windows 8.1 cerification - APTCA Check failed

On Wed, Jan 29, 2014 at 1:21 AM, Uwe Seibt wrote: > > Dear sirs, > > how is it possible to pass the APTCA Check test? Our Application is using .NET Framework 2.0 and .NET Framework 3.5 I doubt you'll get a lot of feedback on this, as this is the "SQLite mailing list" not the

Re: [sqlite] Order of rows in a VALUES select expression

ist > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Scott Robison ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

  1   2   3   4   >