Re: [sqlite] Student's t-test table
if it serves to someone I have attached it regards 1966bc On Sun, Nov 16, 2014 at 8:56 AM, Giuseppe Costanzi giuseppecosta...@gmail.com 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, Simon Slavin slav...@bigfraud.org wrote: On 16 Nov 2014, at 7:39am, Giuseppe Costanzi giuseppecosta...@gmail.com wrote: do you know if a database exists in sqlite with the values, degrees of fredom vs probability (alfa) of the t Student? If you can find one in text or .csv format, we can tell you how to import it. Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Student's t-test table
Hi Giuseppe, On 16 November 2014 00:28, Giuseppe Costanzi giuseppecosta...@gmail.com 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 xmpp: jungle-boo...@jit.si ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Student's t-test table
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 VALUES('1', 3.078, 6.314, 12.706, 31.82,
63.657, 127.321, 318.309, 636.619);
INSERT INTO distribuitions VALUES('2', 1.886, 2.92, 4.303, 6.965,
9.925, 14.089, 22.327, 31.599);
INSERT INTO distribuitions VALUES('3', 1.638, 2.353, 3.182, 4.541,
5.841, 7.453, 10.215, 12.924);
INSERT INTO distribuitions VALUES('4', 1.533, 2.132, 2.776, 3.747,
4.604, 5.598, 7.173, 8.61);
INSERT INTO distribuitions VALUES('5', 1.476, 2.015, 2.571, 3.365,
4.032, 4.773, 5.893, 6.869);
INSERT INTO distribuitions VALUES('6', 1.44, 1.943, 2.447, 3.143,
3.707, 4.317, 5.208, 5.959);
INSERT INTO distribuitions VALUES('7', 1.415, 1.895, 2.365, 2.998,
3.499, 4.029, 4.785, 5.408);
INSERT INTO distribuitions VALUES('8', 1.397, 1.86, 2.306, 2.897,
3.355, 3.833, 4.501, 5.041);
INSERT INTO distribuitions VALUES('9', 1.383, 1.833, 2.262, 2.821,
3.25, 3.69, 4.297, 4.781);
INSERT INTO distribuitions VALUES('10', 1.372, 1.812, 2.228, 2.764,
3.169, 3.581, 4.144, 4.587);
INSERT INTO distribuitions VALUES('11', 1.363, 1.796, 2.201, 2.718,
3.106, 3.497, 4.025, 4.437);
INSERT INTO distribuitions VALUES('12', 1.356, 1.782, 2.179, 2.681,
3.055, 3.428, 3.93, 4.318);
INSERT INTO distribuitions VALUES('13', 1.35, 1.771, 2.16, 2.65,
3.012, 3.372, 3.852, 4.221);
INSERT INTO distribuitions VALUES('14', 1.345, 1.761, 2.145, 2.625,
2.977, 3.326, 3.787, 4.14);
INSERT INTO distribuitions VALUES('15', 1.341, 1.753, 2.131, 2.602,
2.947, 3.286, 3.733, 4.073);
INSERT INTO distribuitions VALUES('16', 1.337, 1.746, 2.12, 2.584,
2.921, 3.252, 3.686, 4.015);
INSERT INTO distribuitions VALUES('17', 1.333, 1.74, 2.11, 2.567,
2.898, 3.222, 3.646, 3.965);
INSERT INTO distribuitions VALUES('18', 1.33, 1.734, 2.101, 2.552,
2.878, 3.197, 3.61, 3.922);
INSERT INTO distribuitions VALUES('19', 1.328, 1.729, 2.093, 2.539,
2.861, 3.174, 3.579, 3.883);
INSERT INTO distribuitions VALUES('20', 1.325, 1.725, 2.086, 2.528,
2.845, 3.153, 3.552, 3.85);
INSERT INTO distribuitions VALUES('21', 1.323, 1.721, 2.08, 2.518,
2.831, 3.135, 3.527, 3.819);
INSERT INTO distribuitions VALUES('22', 1.321, 1.717, 2.074, 2.508,
2.819, 3.119, 3.505, 3.792);
INSERT INTO distribuitions VALUES('23', 1.319, 1.714, 2.069, 2.5,
2.807, 3.104, 3.485, 3.768);
INSERT INTO distribuitions VALUES('24', 1.318, 1.711, 2.064, 2.492,
2.797, 3.09, 3.467, 3.745);
INSERT INTO distribuitions VALUES('25', 1.316, 1.708, 2.06, 2.485,
2.787, 3.078, 3.45, 3.725);
INSERT INTO distribuitions VALUES('26', 1.315, 1.706, 2.056, 2.479,
2.779, 3.067, 3.435, 3.707);
INSERT INTO distribuitions VALUES('27', 1.314, 1.703, 2.052, 2.473,
2.771, 3.057, 3.421, 3.69);
INSERT INTO distribuitions VALUES('28', 1.313, 1.701, 2.048, 2.467,
2.763, 3.047, 3.408, 3.674);
INSERT INTO distribuitions VALUES('29', 1.311, 1.699, 2.045, 2.462,
2.756, 3.038, 3.396, 3.659);
INSERT INTO distribuitions VALUES('30', 1.31, 1.697, 2.042, 2.457,
2.75, 3.03, 3.385, 3.646);
INSERT INTO distribuitions VALUES('31', 1.309, 1.695, 2.04, 2.453,
2.744, 3.022, 3.375, 3.633);
INSERT INTO distribuitions VALUES('32', 1.309, 1.694, 2.037, 2.449,
2.738, 3.015, 3.365, 3.622);
INSERT INTO distribuitions VALUES('33', 1.308, 1.692, 2.035, 2.445,
2.733, 3.008, 3.356, 3.611);
INSERT INTO distribuitions VALUES('34', 1.307, 1.691, 2.032, 2.441,
2.728, 3.002, 3.348, 3.601);
INSERT INTO distribuitions VALUES('35', 1.306, 1.69, 2.03, 2.438,
2.724, 2.996, 3.34, 3.591);
INSERT INTO distribuitions VALUES('36', 1.306, 1.688, 2.028, 2.434,
2.719, 2.991, 3.333, 3.582);
INSERT INTO distribuitions VALUES('37', 1.305, 1.687, 2.026, 2.431,
2.715, 2.985, 3.326, 3.574);
INSERT INTO distribuitions VALUES('38', 1.304, 1.686, 2.024, 2.429,
2.712, 2.98, 3.319, 3.566);
INSERT INTO distribuitions VALUES('39', 1.304, 1.685, 2.023, 2.426,
2.708, 2.976, 3.313, 3.558);
INSERT INTO distribuitions VALUES('40', 1.303, 1.684, 2.021, 2.423,
2.704, 2.971, 3.307, 3.551);
INSERT INTO distribuitions VALUES('42', 1.302, 1.682, 2.018, 2.418,
2.698, 2.963, 3.296, 3.538);
INSERT INTO distribuitions VALUES('44', 1.301, 1.68, 2.015, 2.414,
2.692, 2.956, 3.286, 3.526);
INSERT INTO distribuitions VALUES('46', 1.3, 1.679, 2.013, 2.41,
2.687, 2.949, 3.277, 3.515);
INSERT INTO distribuitions VALUES('48', 1.299, 1.677, 2.011, 2.407,
2.682, 2.943, 3.269, 3.505);
INSERT INTO distribuitions VALUES('50', 1.299, 1.676, 2.009, 2.403,
2.678, 2.937, 3.261, 3.496);
INSERT INTO distribuitions VALUES('60', 1.296, 1.671, 2.0, 2.39,
2.66, 2.915, 3.232, 3.46);
INSERT INTO distribuitions VALUES('70', 1.294, 1.667, 1.994, 2.381,
2.648, 2.899, 3.211, 3.435);
INSERT INTO distribuitions VALUES('80', 1.292, 1.664, 1.99, 2.374,
2.639, 2.887, 3.195, 3.416);
INSERT INTO distribuitions VALUES('90', 1.291, 1.662, 1.987, 2.369,
2.632, 2.878, 3.183, 3.402);
INSERT INTO
[sqlite] Verifying a file is valid SQLite3
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, i.e. if you do not find these exact bytes as this exact offset, then it definitely isn't an SQLite3 file. If this is documented somewhere, a link would suffice - thanks! ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Verifying a file is valid SQLite3
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 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, i.e. if you do not find these exact bytes as this exact offset, then it definitely isn't an SQLite3 file. If this is documented somewhere, a link would suffice - thanks! ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Verifying a file is valid SQLite3
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, 2014 at 5:03 AM, RSmith rsm...@rsweb.co.za wrote: 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, i.e. if you do not find these exact bytes as this exact offset, then it definitely isn't an SQLite3 file. If this is documented somewhere, a link would suffice - thanks! ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Is this a bug? autoincrement in int primary key vs integer primary key
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 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 - VSC processing made easy ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Is this a bug? autoincrement in int primary key vs integer primary key
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 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Is this a bug? autoincrement in int primary key vs integer primary key
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 i...@tandetnik.org: 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 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Bernardo Sulzbach ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Is this a bug? autoincrement in int primary key vs integer primary key
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 - VSC processing made easy On 16 November 2014 16:07, Bernardo Sulzbach mafagafogiga...@gmail.com wrote: 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 i...@tandetnik.org: 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 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Bernardo Sulzbach ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Discrepancy with indexing and WHERE clause with AND/OR
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 prakash.p...@gmail.com who is apparently quite determined to go this route. I think judicious use of the available hints (i.e. CROSS JOIN and USING) will get you further quicker. We almost exclusively use virtual tables here (for which ANALYZE is useless) and find CROSS JOIN to be our best friend in fixing queries that xBestIndex return values cannot coax into performing well. -Ursprüngliche Nachricht- Von: RP McMurphy [mailto:rpm0...@yahoo.com] Gesendet: Freitag, 14. November 2014 15:32 An: sqlite-users@sqlite.org Betreff: Re: [sqlite] Discrepancy with indexing and WHERE clause with AND/OR I am resending this message below from 3 days ago because it never made it to the list. RP PS: Messages seem to take a long time to go through the gmane system, at least half a day and sometimes more in my experience so far. On Tue, 11/11/14, RP McMurphy rpm0...@yahoo.com wrote: Subject: Re: Discrepancy with indexing and WHERE clause with AND/OR To: sqlite-users@sqlite.org Date: Tuesday, November 11, 2014, 6:31 PM If you can provide any examples where ANALYZE makes a query slower, I suspect the developer team would like to see them. After we run analyze and then let the process run for a while the DB contents change - and it can change quite considerably depending upon what is happening. I suspect that the analyze data gets stale, but I don't know how to track such things in sqlite. Anyhow we can't keep running analyze every few minutes because it takes a long time to run with our DB and it appears to block all other actions until it is done. A this point we are considering writing VDBE code directly and bypassing the parser. Has anyone else done this? Is it going to be a huge ugly can-of-worms if we do that? RP ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users ___ Gunter Hick Software Engineer Scientific Games International GmbH FN 157284 a, HG Wien Klitschgasse 2-4, A-1130 Vienna, Austria Tel: +43 1 80100 0 E-Mail: h...@scigames.at This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
