We encountered a doubly freed "C" pointer after calling sqlite3_exec
in my custom version of the Microsoft.Data.Sqlite C# method
SqliteCommand::ExecuteAnReader which does not call the parent C# class
method DbCommand::ExecuteReader which does not use a C# NativeMethod. The
C# NativeMethod clas
2015-11-14 20:53 GMT+01:00 Keith Medcalf :
> SQLite version 3.8.8.3 2015-02-25 13:29:11
> Enter ".help" for usage hints.
> Connected to a transient in-memory database.
> Use ".open FILENAME" to reopen on a persistent database.
>
> If I use that version of the amalgamation, I cannot seem to compile
On 11/14/15, Igor Korot wrote:
> Hi, Richard,
>
> On Sat, Nov 14, 2015 at 6:54 PM, Richard Hipp wrote:
>> On 11/14/15, Igor Korot wrote:
>>> Hi, ALL,
>>> I am trying to use following query:
>>>
>>> "PRAGMA table_info(?)"
>>
>> The argument to a pragma is not an expression, and hence it cannot us
Hi, Richard,
On Sat, Nov 14, 2015 at 6:54 PM, Richard Hipp wrote:
> On 11/14/15, Igor Korot wrote:
>> Hi, ALL,
>> I am trying to use following query:
>>
>> "PRAGMA table_info(?)"
>
> The argument to a pragma is not an expression, and hence it cannot use
> bound parameters.
Thank you for that ex
On 11/14/15, Igor Korot wrote:
> Hi, ALL,
> I am trying to use following query:
>
> "PRAGMA table_info(?)"
The argument to a pragma is not an expression, and hence it cannot use
bound parameters.
--
D. Richard Hipp
drh at sqlite.org
Hi, ALL,
I am trying to use following query:
"PRAGMA table_info(?)"
with the sqlite3_prepare_v2()/sqlite3_bind()/sqlite3_step() sequence.
However the call to sqlite3_prepare_v2() fails with the SQLITE_ERROR or
the value of 1.
The following call to sqlite3_ermsg() says "near "?": syntax error".
Windows 10 1511 includes both a 64-bit and 32-bit version of SQLite called:
C:\Windows\System32\winsqlite3.dll
C:\Windows\SysWow64\winsqlite3.dll
for the 64-bit and 32-bit versions respectively.
The version of SQLite contained in these libraries is:
2015-02-25 13:29:11 9d6c1880fb75660bbabd6931
On Fri, Nov 13, 2015 at 11:55 PM, Stephen Chrzanowski
wrote:
> Prior to release or otherwise, it feels that if MSoft were to have skipped
> the registry and just used the GROUP->KEY=VALUE setup in INI files only,
> things would be much better as far as cleaning up viruses at LEAST,
> especially i
I'm doing a select like this:
select e.name, e.release from execution as e where run_id
in (select substr(status,7,5) from resource where status like "Busy (%");
I want to get to get a column from each row of the subselect (from
resource) to match each result row.
resource table:
name status
se
SQLite version 3.9.2 2015-11-02 18:31:45
sqlite> .header on
sqlite> select 0x1zzz;
zzz
1
sqlite>
Prior to release or otherwise, it feels that if MSoft were to have skipped
the registry and just used the GROUP->KEY=VALUE setup in INI files only,
things would be much better as far as cleaning up viruses at LEAST,
especially if you start locking down these files at the NTFS level. But
then again
I've read through all the other posts on this thread, and I must agree.
Your "serverless" configuration can't exist because each client becomes a
server, BY DEFINITION, when it starts PROVIDING information to other
clients.
I've written a book, by now, when this topic comes up. Believe me
Alessan
On 11/14/2015 12:33 AM, Johnny Wezel wrote:
> I think there is a flaw in information passing between the xBestIndex
> and xFilter methods in virtual tables.
>
> The information about the constraint operation in the aConstraint array
> can't reach xFilter. But how is xFilter to know how to set up th
13 matches
Mail list logo
