OK, thanks for the detailed analysis! :-)
Am Tue, 09 May 2017 16:06:28 -0600 schrieb Keith Medcalf:
[...]
> If Windows reports that the filesystem is "local" then it is OK. If
> Windows reports that the filesystem is "remote", then it is ungood. A
> "drive mapped to the local computer" is a
Interesting idea; when I've finished diagnosing my current problem, it might be
worth expanding the repertoire of the Android library.
I presume that the sqlite logging function could be used to get the message at
least, is that correct? IIRC, it's called on an error and the OS file-related
er
Klaas Van B. wrote:
" Indeed, in the page you refer to is missing the operator "<>" documented here:
"
"
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsqlite.org%2Frowvalue.html%23syntax&data=02%7C01%7CStephan.Mueller%40microsoft.com%7C1581cbb9304944c7d4d208d496d91ad4%7C72f988bf8
> Le 9 mai 2017 à 15:41, Gwendal Roué a écrit :
>
>>> As a reminder, I intend to use the authorisation system in order to tell if
>>> a statement has an opportunity to impact on another statement, as a support
>>> for a general database observation feature.
>>
>> How are you going to handle T
On Wed, May 10, 2017 at 1:35 PM, Gwendal Roué
wrote:
> > Le 9 mai 2017 à 15:41, Gwendal Roué a écrit :
> >> How are you going to handle TRIGGERs ?
> >
> > That's a very good question.
>
> Very good news: foreign keys and triggers are 100% handled by authorizer
> callbacks, for free :-D
>
Thanks
Good day -
I just downloaded & built sqlite-autoconf-318 on Linux x86_64 .
Now I would like run some some 'test suite' that will allow me to
determine if the build is OK - but there appears to be none :
$ make check
make: Nothing to be done for 'check'.
(no test runs are done - this appears
On 10 May 2017, at 2:26pm, Jason Vas Dias wrote:
> I just downloaded & built sqlite-autoconf-318 on Linux x86_64 .
>
> Now I would like run some some 'test suite' that will allow me to
> determine if the build is OK - but there appears to be none :
What you have there is the amalgamation s
On 5/10/17, Jason Vas Dias wrote:
>
> Now I would like run some some 'test suite' that will allow me to
> determine if the build is OK - but there appears to be none :
>
As Simon already pointed out, you have download the pre-compiled
"amalgamation" sources. That tarball does not include any tes
> Le 10 mai 2017 à 15:06, Dominique Devienne a écrit :
>
> On Wed, May 10, 2017 at 1:35 PM, Gwendal Roué
> wrote:
>
>>> Le 9 mai 2017 à 15:41, Gwendal Roué a écrit :
How are you going to handle TRIGGERs ?
>>>
>>> That's a very good question.
>>
>> Very good news: foreign keys and trigg
On 5/10/17, Dominique Devienne wrote:
>
> We haven't heard from Richard, but I hope we will eventually.
>
No new authorizer codes will be added, since that would present
compatibility problems for legacy authorizer callbacks. Instead, the
fix is to invoke the authorizer callback with SQLITE_READ
Scott Robison wrote...
Yes, it might just need to walk through a larger data set. If nulls are
rare, there probably wouldn't be much of a difference (not in front of a
computer to check). If the column was mostly nulls, and a lot of rows, it
might be a lot faster.
Hmmm... Thanks. I have lots
Thanks for the clever ideas. In my case I figured it out by hand (it was a
trigger which was inserting a row with a foreign key into another table
that no longer existed). But I will make use of those strategies in the
future.
On Tue, May 9, 2017 at 11:54 PM, Gwendal Roué
wrote:
> There is a
Richard. Further to your reply on Mar 31 2017, were those newly worked
code exemplars demonstrating non-trivial sqlite3_index_info from xBestIndex
interaction for a SQLite table backed vtable published?
I am sure there is still great interest for this information considering
the lack of even one
Hello.
We have a DB with a corrupted index (see below). The database has a max_pages
limit that works out to a 10 MB database size (we're embedded).
We can insert into the table the index is on OK.
When we do a SELECT out of the table that uses the index, we get a "disk or
database full" erro
On 10 May 2017, at 6:31pm, Ward WIllats wrote:
> I guess with corruption, all bets are off
I see your results from "pragma integrity_check". As you write, "all bets are
off".
If your database is corrupt, any operation on it might silently lead to more
corruption. It may just happen that y
Hi everyone,
I’m having a hard time getting Entity Framework 6 to work with a password
encrypted file. I’ve tried several things the last few days and just cannot get
it to work, I always get an error stating that the file is encrypted. My
connection string with a password looks like this:
T
> On May 10, 2017, at 10:49 AM, Simon Slavin wrote:
>
> On 10 May 2017, at 6:31pm, Ward WIllats wrote:
>
>> I guess with corruption, all bets are off
>
> I see your results from "pragma integrity_check". As you write, "all bets
> are off".
Thanks Simon. I'm not saying there is any kind o
On 10 May 2017, at 9:26pm, Ward WIllats wrote:
> But, we didn't do this in this case because a "disk full" error is not the
> CORRUPT or NOTADB error we expected to see to trigger the panic. So I was
> surprised, but...
I suspect that your initial post is correct, and the "disk full" error is
> On May 10, 2017, at 2:20 PM, Simon Slavin wrote:
> I’m concerned that this sort of corruption is happening repeatedly. Whether
> or not there’s anything in howtocorrupt.html that rings any bells, you can
> rely on us to help figure out what’s wrong.
>
Thanks. That's kind. It could well be
On 5/10/17, Ward WIllats wrote:
>
> The unusual parts of our setup are:
>
> 1. The DB in questions is on a volatile filesystem and ATTACHED to another,
> smaller one residing on a flash (JFFS) filesystem, and
> 2. We use the shady SQLITE_SHM_DIRECTORY compile switch to move the .shm
> file off JFF
> On May 10, 2017, at 10:49 AM, Simon Slavin wrote:
>
> On 10 May 2017, at 6:31pm, Ward WIllats wrote:
>
>> I guess with corruption, all bets are off
>
> I see your results from "pragma integrity_check". As you write, "all bets
> are off".
Thanks Simon. I'm not saying there is any kind o
> Le 10 mai 2017 à 18:22, Richard Hipp a écrit :
>
> On 5/10/17, Dominique Devienne wrote:
>>
>> We haven't heard from Richard, but I hope we will eventually.
>>
>
> No new authorizer codes will be added, since that would present
> compatibility problems for legacy authorizer callbacks. Ins
22 matches
Mail list logo