Got the latest [3392f8fa] fix from the trunk but now get these
errors/warnings:
./sqlite3.c:27509:42: error: expected expression before ?,? token
{ "munmap", (sqlite3_syscall_ptr),0 },
^
./sqlite3.c:27387:12: warning:
Just to confirm that if sqlite3.dll is compiled with
DSQLITE_DEFAULT_PCACHE_INITSZ=0
I can also see memory being released here.
So, that was indeed it.
RBS
On Thu, Jan 7, 2016 at 11:04 PM, Scott Hess wrote:
> Hmm. I see that sqlite3PcacheReleaseMemory() is a no-op
> if
(Under Linux)
I?m using the SQLITE_OMIT_WAL option and because of this the #define osReadlink
is not defined (amalgamation line # 27508) which is later required by
unixFullPathname function, and compilation fails.
Thanks.
*** SORRY IF YOU HAVE RECEIVED THIS TWICE ? NOT SURE IT MADE IT THE
I am interested to know from the statement string if the statement is
invalid, row producing (could produce rows) or non row producing. I know
sqlite3_prepare16_v2 can see if the statement is valid or not but how about
the other 2?
I can do this in code no problem, but it may not always be 100%
On 2016/01/08 9:51 AM, Darren Duncan wrote:
> Stephen,
>
> What you are arguing for (no shared libraries) is bad old days where
> one had to recompile their programming language to add support for a
> DBMS, rather than the DBMS support being a separately installable
> library that one could
Okay, I think this clears some things up.
On 2016-01-08 11:36 AM, Warren Young wrote:
> On Jan 8, 2016, at 12:39 AM, Darren Duncan wrote:
>>
>> I interpreted your request as if current systems' error outputs at execute
>> time were printing out the problematic SQL statement with placeholder
On 2016-01-08 8:08 AM, Stephen Chrzanowski wrote:
> For the record, *I* personally prefer trying to get all essential resources
> built directly into my final output (For SQLite, default database
> structures, SQLite strings, and maybe that one day, SQLite itself), that
> way I'm in control of
You can create a custom tokenizer as well then use the standard search
APIs. I imagine that functionality would work well in this case:
https://sqlite.org/fts5.html#section_7
On Thu, Jan 7, 2016 at 3:59 PM, Stadin, Benjamin <
Benjamin.Stadin at heidelberg-mobil.com> wrote:
> One such algorithm
With fts4 you could search for matching terms in an fts4aux table, then use
those to construct a query against the original table. You'd have a full
scan of the fts index, but you'd not have to do a full table scan of the
primary data. Unfortunately if there were a large number of hits in the
On Jan 8, 2016, at 12:39 AM, Darren Duncan wrote:
>
> I interpreted your request as if current systems' error outputs at execute
> time were printing out the problematic SQL statement with placeholder names
> as originally prepared, and you wanted the error outputs to have the
> placeholders
On Fri, Jan 8, 2016 at 10:54 AM, R Smith wrote:
>
> I can't agree more - and to add, while I can sympathize with the point, I
> absolutely love SQLite, but the amount of projects I have made without
> SQLite far outweighs those containing it (on all platforms). I would like
> it to remain
Because this list supports many different things, not just SQLite
downloaded from sqlite.org, maybe I'm off target with my interpretation of
these wishlists.
I'm not arguing about pros and cons of shared libraries directly. My
comments were made from a tired guy who started the day early, was
Bug report
I downloaded sqlite 3.10.0 released in 2016-1-6, earlier I downloaded sqlite
3.9.2 and earlier version.
I found below 2 bugs:
bug1: Database directory which contains Simplified Chinese Character not
support.
bug2: Simplified Chinese Character in database table display error.
bug1:
This is how R works too. That is the RSQLite package that gives
access to SQLite includes SQLite itself right in the package itself so
one need not separately install SQLite.
Also RSQlite uses the R DBI package which defines connections as
classes which are subclassed by the various database
On Fri, Jan 8, 2016 at 12:14 AM, James K. Lowden
wrote:
> I would like to see a strict mode, too.
+1
> I would also like to be able to make "strictness" a property of the
> database, not the connection.
>
+1
similarly I'd like enforcing FKs to be per database, not per connection.
> One way
On 8 Jan 2016, at 12:22am, Jim Callahan
wrote:
> The existing SQLite APIs are correct, but hard to use in the
> sense that creating an interface from an OOIL language is more involved
> than just "wrapping" one by one a set of functions. What I am proposing is
> a second set of APIs that when
06-01-2016, Scott Perry:
The SQLite built into OS X does not support cache sharing for performance
reasons?, which is probably why your results are statistically identical and
the OP's results are wildly different.
You can verify this by checking the return value of
sqlite3_enable_shared_cache;
17 matches
Mail list logo
