[sqlite] Sqlite3 stable version
Dear drh, We do want install the latest version of sqlite.for the production ( 2007-Apr-09 - Version 3.3.15 ) But, Our sytem group, found the only flaged stable version of the sqlite3 in the web site is this one ( 2006-Jan-31 - Version 3.3.3 stable ) The question? Are all the sqlite-x.x.x other than (Version 3.3.3 stable) not stable, or the word stable is just missing from the latest releases. or the word stable is just used for the transition from sqlite-2.8.x to sqlite3.x.x.? Thanks you for help! hb - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] sqlite-3.3.3 coredumps on SGI IRIX64
[EMAIL PROTECTED] wrote: Hamid Benhocine <[EMAIL PROTECTED]> wrote: Hello, I m trying to upgrade from sqlite-3.2.7 on SGI IRIX64 to sqlite-3.3.3 The applications using sqlite-3.2.7 (compiled with mode 64 or 32 bits) work fine. But the upgrade to sqlite-3.3.3 coredump on 64 bits when creating tables with the UNIQUE, PRIMARY constraints. People with 64-bit alignment sensitive machines: Please tell me if check-in [3079] solves your problems. http://www.sqlite.org/cvstrac/chngview?cn=3079 -- D. Richard Hipp <[EMAIL PROTECTED]> replacing build.c table.c and sqliteInt.h ins sqlite-3.3.3 with those of ticket 3079 all the Problems are fixed I was able to run the regression tests and the results are 5 errors out of 23846 tests Failures on these tests: printf-8.2 sync-1.1 sync-1.2 sync-1.3 types3-1.3 (they are related to tcl!!) GREAT JOB. thanks a lot. Hamid
[sqlite] sqlite-3.3.3 coredumps on SGI IRIX64
Hello, I m trying to upgrade from sqlite-3.2.7 on SGI IRIX64 to sqlite-3.3.3
The applications using sqlite-3.2.7 (compiled with mode 64 or 32 bits) work
fine. But the upgrade to sqlite-3.3.3 coredump on 64 bits when creating
tables
with the UNIQUE, PRIMARY constraints. I did not run in this issue with the
earlier versions (sqlite-3.2.5--> sqlite-3.2.7).
May be can any one help.
thanks
Hamid
irix64% cat test.sql
CREATE TABLE t ( a INTEGER NOT NULL, b INTEGER NOT NULL, rval REAL ,
UNIQUE(a,b));
irix64% sqlite64 test.db
SQLite version 3.2.7
Enter ".help" for instructions
sqlite> .read test.sql
sqlite> .schema
CREATE TABLE t ( a INTEGER NOT NULL, b INTEGER NOT NULL, rval REAL ,
UNIQUE(a,b));
sqlite> .quit
irix64% rm test.db
irix64% ./sqlite test.db
SQLite version 3.3.3
Enter ".help" for instructions
sqlite> .read test.sql
Bus error(coredump)
irix64% rm test.db
irix64% rm core
irix64% dbx ./sqlite
dbx version 7.3.7 (96015_Nov16 MR) Nov 16 2004 07:34:16
Executable /home/afsd/hmd/tmp/sqlite-3.3.3/./sqlite
(dbx) r test.db
Process 345139655 (sqlite) started
SQLite version 3.3.3
Enter ".help" for instructions
sqlite> .read test.sql
Process 345139655 (sqlite) stopped on signal SIGBUS: Bus error (default)
at [sqlite3CreateIndex:2421 +0x18,0x1004bae8]
2421 pIndex->azColl[i] = zColl;
(dbx) where
> 0 sqlite3CreateIndex(pParse = 0xfff8040, pName1 = (nil), pName2
= (nil), pTblName = (nil), pList = 0x100896d0, onError = 99, pStart =
(nil), pEnd = (nil), sortOrder = 0, ifNotExist = 0)
["/home/afsd/hmd/tmp/sqlite-3.3.3/build.c":2421, 0x1004bae8]
1 yy_reduce(yypParser = 0x10090c38, yyruleno = 87)
["/home/afsd/hmd/tmp/sqlite-3.3.3/parse.y":315, 0x100390f4]
2 sqlite3Parser(yyp = 0x10090c38, yymajor = 20, yyminor = struct Token {
z = 0x1008a96a = ");"
dyn = 0
n = 1
}, pParse = 0xfff8040)
["/home/afsd/hmd/tmp/sqlite-3.3.3/parse.c":3218, 0x1003b820]
3 sqlite3RunParser(pParse = 0xfff8040, zSql = 0x1008a918 =
"CREATE TABLE t ( a INTEGER NOT NULL, b INTEGER NOT NULL, rval REAL ,
UNIQUE(a,b));", pzErrMsg = 0xfff8020)
["/home/afsd/hmd/tmp/sqlite-3.3.3/tokenize.c":391, 0x10037df0]
4 sqlite3_prepare(db = 0x1008a978, zSql = 0x1008a918 = "CREATE TABLE
t ( a INTEGER NOT NULL, b INTEGER NOT NULL, rval REAL ,
UNIQUE(a,b));", nBytes = -1, ppStmt = 0xfff8198, pzTail =
0xfff81b8) ["/home/afsd/hmd/tmp/sqlite-3.3.3/prepare.c":539, 0x100364e4]
5 sqlite3_exec(db = 0x1008a978, zSql = 0x1008a918 = "CREATE TABLE t (
a INTEGER NOT NULL, b INTEGER NOT NULL, rval REAL , UNIQUE(a,b));",
xCallback = 0x1000b2a0, pArg = 0xfffa1f8, pzErrMsg = 0xfff8250)
["/home/afsd/hmd/tmp/sqlite-3.3.3/legacy.c":56, 0x100759f8]
6 process_input(p = 0xfffa1f8, in = 0xdb31088)
["/home/afsd/hmd/tmp/sqlite-3.3.3/shell.c":1487, 0x10010130]
7 do_meta_command(zLine = 0x10089848 = ".read", p = 0xfffa1f8)
["/home/afsd/hmd/tmp/sqlite-3.3.3/shell.c":1219, 0x1000ed28]
8 process_input(p = 0xfffa1f8, in = (nil))
["/home/afsd/hmd/tmp/sqlite-3.3.3/shell.c":1456, 0x1000fe48]
The sqlite-3.2.7 and sqlite-3.3.3 are compiled
this way
rm tclsqlite.c libsqlite.a sqlite 2> /dev/null
for i in *.c
do
echo $i
cc -64 -g -c $i
done
rm shell.o
ar scru libsqlite.a *.o
cc -64 -g -o sqlite shell.c libsqlite.a
Re: [sqlite] Proposed 3.3.0 changes. Was: 5/2==2
Dennis Cote wrote:
The second issue is demonstrated by the last last three statements.
CREATE TABLE t (a REAL, b REAL);
INSERT INTO t VALUES (5, 2);
SELECT a / b FROM t;
Here he has explicitly declared the columns a and b to be of type
real. He then stores integer literal values into those columns. This
is where the problem occurs, not during the division in the select
statement.
SQL is a typed language. SQLite was originally an untyped
implementation of SQL. In version 3 SQLite was changed to introduce
stronger data typing, while still trying to maintain compatibility
with its previous untyped versions. It does this very well in most
cases. SQLite uses manifest typing, where each data value has its own
associated data type whereas the standard assumes each column has a
data type. In a few cases SQLite bumps into areas where this
implementation produces non-standard behavior. This is one of them.
To produce standard behavior, integer values stored into columns of
type real should be converted to real values.
This is actualy the problem we have,
even we take care of inserting /or importing data doing the right
bindings (to fellow the example above)
and it's diffult to care of everything ..
rc = sqlite3_prepare(db, "insert into t values (?,?);", -1, , 0);
if (rc == SQLITE_OK && stmt != NULL ) {
sqlite3_bind_double(stmt, 1, 5);
sqlite3_bind_double(stmt, 2, 2);
sqlite3_step(stmt);
rc = sqlite3_reset(stmt);
}
rc = sqlite3_finalize(stmt);
sqlite3> select a,b,(a/b) from t
5.0|2.0|2.5 Ok.
when a user issue an update command (i have no control on this command)
on the two columns with
sqlite3> update set a= 5, b =2;
sqliote3> select a,b,(a/b) from t;
5|2|2 which is not correct.
But i don't see a problem when explictly doing 5/2 gives 2. AS 5 and 2
are integers.
regards
hamid
Re: [sqlite] where can I find resources of using sqlite in Python?
刘瑞展 wrote: hello, where can I find resources of using sqlite in Python? thanks a lot liu http://www.rogerbinns.com/apsw.html http://initd.org/tracker/pysqlite regards hb.
Re: [sqlite] FYI: Fortran interface to SQLite
Hello, Very interesting, I planned to do some work (not done yet) to provide my division with some examples using sqlite with fortran 90/95 (to replace a home pivot format in numerical computing : we use f90/95). So, if you have a release, you want to share, I will be happy to test it on our Unix platforms(IBM , SGI, Linux) with the Fortran 90/95 compilers - IBM XL Fortan Compiler ( 64/32 bits Mode), - SGI Mips Pro F90/95 Compiler (64/32 bits)., - PGF f90/95 (Portland Group) Regards. Hamid Arjen Markus wrote: Hello, my (almost) first experience with SQLite was the sample code that Al Danial published to show how to use SQLite in a FORTRAN program. I was inspired by his work to develop a more comprehensive interface, this time in Fortran 90/95. I am pleased to say that this was fairly easy to do and that it is nearing a stage where I dare release it in the wild. The idea: - Provide a library that hides as much as possible the detail of Fortran-C interfacing - Provide low-level routines for flexibility and some high-level routines for common tasks and ease of use. It has been tested on Windows with Compaq Visual Fortran and MS VC/C++ only so far, but it should not be a problem to get to work with other common compiler combinations. Anyone who is interested, just drop a note. Regards, Arjen
Re: [sqlite] Please Need Advice on 64 Bits Platform
Hi, IBM : powerpc-ibm-aix5.1.0.0 I did a lot of cleanup in environnemnts variables. then 1 ) export OBJECT_MODE=64 2) I stick with a simple configure ./../sqlite-3.2.7/configure --disable--shared --disable-tcl --disable-threadsafe --prefix=$PREFIX 3) in the Makefile put -q64 -qlonglong for the xlc compiler 4) in ./libtool forced ar with -X64 flag results: SQLite Works fine . I did some basics tests (inserts,simple selects, create temp tables ..) I think , Now people here, will certainly consider this very great Engine to suit there needs.. and replace the . home data format. Thansks all and thanks drh. I will post if i have trouble. Hamid. Jarosław Nozderko wrote: I've just built SQLite 3.2.7 on HP-UX 11 in 64-bit mode. Loading 1000 000 records into a simple table (using .read from SQL script with inserts, 1 in a single transaction) took 5 min 40 s (the same in 32-bit - 06:29) and creating index 56 s (01:14 for 32-bit). Unfortunately, this is heavily loaded server, so results above may not be precise. Regards, Jarek Hamid Benhocine <[EMAIL PROTECTED]> wrote: I want just to know if the Engine is 64 bits ready SQLite is designed to work on 64-bit machines. There have been a few alignment problems in the past but those have all been worked out now, I believe. I do not have a 64-bit machine to test on, but reports from users are that SQLite works when compiled in 64-bit mode. -- D. Richard Hipp <[EMAIL PROTECTED]>
[sqlite] Please Need Advice on 64 Bits Platform
Hi all, I am always on the lookout for simple yet powerful software development tools and SQLite definitely falls into this category. It is a very great software. I tested the software a lot to replace our home data format (for Meteroligical Observations). The engine is very very fast for insertion of millions of records of satellite data. All the job was carried on Linux, SGI IRIX64 (front ends) The software was compiled in 32 bits mode. I did also some tests on our SuperComputer IBM (Aix v 5.1) and SQlite work great when Compiled in 32 b mode (-q32 -qlonglong VisualAge xlc flags etc). Because every peace of software we use on IBM must compile in 64 bits mode, ( I did not succeed to run Sqlite When Compiled iin 64 bits mode And I'm not a Sofware Engeneer) I want just to know if the Engine is 64 bits ready (the boss langage) or Can we call Sqlite (Complied 32 bits) from 64 bits applications. Any advice is Welcome. I worked very hard to push Sqlite to replace our home data format (Sqlite will do Solve a lot of our pbs .) Thanks A lot. Hamid
