I would agree with the suspicion that your data is "changing shape" i.e. the
cardinality of index fields is becoming very different from what ANALYZE stored.
As for bypassing the query planner/code generator you might want to contact
Prakash Premkumar who is apparently
Thanks for the link Bernard
Paul
www.sandersonforensics.com
skype: r3scue193
twitter: @sandersonforens
Tel +44 (0)1326 572786
http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit
-Forensic Toolkit for SQLite
http://sandersonforensics.com/forum/content.php?168-Reconnoitre -
You are supposing that INT PRIMARY KEY == INTEGER PRIMARY KEY. Which,
clearly, is not true.
http://stackoverflow.com/questions/20289410/difference-between-int-primary-key-and-integer-primary-key-sqlite
see this link for more on the subject.
2014-11-16 13:56 GMT-02:00 Igor Tandetnik
On 11/16/2014 10:51 AM, Paul Sanderson wrote:
AUTOINCREMENT is only allowed on an INTEGER PRIMARY KEY
No it's not a bug. AUTOINCREMENT is only allowed on INTEGER PRIMARY KEY.
Which part of the error message do you find unclear?
For details, see http://www.sqlite.org/autoinc.html
CREATE TABLE IF NOT EXISTS test (id INTEGER PRIMARY KEY AUTOINCREMENT,
temp text UNIQUE NOT NULL);
works OK
CREATE TABLE IF NOT EXISTS test (id INT PRIMARY KEY AUTOINCREMENT,
temp text UNIQUE NOT NULL);
gives error
AUTOINCREMENT is only allowed on an INTEGER PRIMARY KEY
Paul
OOC I searched 'sqlite file format' and found...
http://www.sqlite.org/fileformat.html
testing the first string bytes will be enough... it's enough for png,
etc...
can validate thate page lengths vs the real length, which is what sqlite
uses to determine 'CORRUPT' plus some...
On Sun, Nov 16,
Nvm - found it - thanks.
It seems the SQlite search engine is better than the Google one - Page ref (in
case anyone else is interested):
https://www.sqlite.org/fileformat2.html#database_header
Specifically point 1.2.1
On 2014/11/16 15:03, RSmith wrote:
Could someone kindly tell me the
Could someone kindly tell me the byte-pattern, offset and length into an SQLite3 file that might suffice to verify that it is indeed
an SQLite3 file.
I am not very concerned with false positives (as nobody can control all the files in the World), but rather interested in absolute
negatives,
ops,I don't have a link,
I think that this is better
BEGIN TRANSACTION;
CREATE TABLE 'distribuitions' (
'v' TEXT,
'p0.20' REAL,
'p0.10' REAL,
'p0.05' REAL,
'p0.02' REAL,
'p0.01' REAL,
'p0.005' REAL,
'p0.002' REAL,
'p0.001' REAL
);
INSERT INTO "distribuitions"
Hi Giuseppe,
On 16 November 2014 00:28, Giuseppe Costanzi wrote:
> if it serves to someone I have attached it
>
Attachments don't come through, post a link to the file.
> regards
> 1966bc
>
Best,
jb
--
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
if it serves to someone I have attached it
regards
1966bc
On Sun, Nov 16, 2014 at 8:56 AM, Giuseppe Costanzi
wrote:
> Thanks Simon, I know how to perform the importation.
> However thanks of the idea.
> I start looking for it.
>
> On Sun, Nov 16, 2014 at 8:46 AM,
11 matches
Mail list logo