[sqlite] Connecting to SQLite with Crystal Reports Writer
Users, I am wanting to connect to a SQLite DB with CRW. Has anyone had any experience doing this? I was thinking of using the SQLite ODBC Driver. Any help would be appreciated Ray Borror
Re: [sqlite] Re: philosophy behind public domain?
Well, since D. Richard Hipp would be the copyright holder if SQLite was licensed, that would be up to him, but he hasnt replied to the update yet. If the licensing policy changes, probably the MIT license or (new/revised) BSD license would be good choices, though it seems to me (as a non-lawyer) that Larry Rosen's AFL would provide better protection against patent problems - but then whether or not it really would affect GPLed code is debatable, and that's not fun if you're just interested in coding. Eugene Wee Darren Duncan wrote: Considering everything brought forth here, can anyone think of a reason not to have SQLite officially released from now on under a permissive free software license like the modified BSD license or the very similar X11 license? Aside from a bit of time to search-n-replace some text, what would we stand to lose from such an action? -- Darren Duncan
Re: [sqlite] Running Sqlite in 64-bit mode on Win XP x64???
On 6/3/05, basil thomas <[EMAIL PROTECTED]> wrote: > To all > Has anyone run sqlite in 64-bit mode on the new Win XP x64 os??? Yup. It is running beautifully for me in PeerGuardian. > Have you been able to create an in memory database greater than 2 > gigabytes??? Can't say I've tried. > What is the performance compared to sqlite in 32-bit mode?? The majority of work is I/O bound, so the performance is about the same. Maybe I can run some tests on in memory databases. > If no to any of the above, can Sqlite run in full 64-bit mode anyway??? > > -- Cory Nelson http://www.int64.org
[sqlite] Running Sqlite in 64-bit mode on Win XP x64???
To all Has anyone run sqlite in 64-bit mode on the new Win XP x64 os??? Have you been able to create an in memory database greater than 2 gigabytes??? What is the performance compared to sqlite in 32-bit mode?? If no to any of the above, can Sqlite run in full 64-bit mode anyway???
[sqlite] how should i configure sqlite3 to move my sqlite3
Hi, Iam new to use sqlite3 OS Linux: my problem is i have to configure and build my sqlite3 transfer that object to another meachine which has less Linux library files when i build and moved the object file to another system of small Linux it asks the files libreadline.so.4. and some files how can i build my sqlite3 such that it can run in any system with considering the libiraries of that system. it will be helpful if the advice with steps thanks in advance selvarajj
[sqlite] Re: philosophy behind public domain?
Considering everything brought forth here, can anyone think of a reason not to have SQLite officially released from now on under a permissive free software license like the modified BSD license or the very similar X11 license? Aside from a bit of time to search-n-replace some text, what would we stand to lose from such an action? -- Darren Duncan
[sqlite] Re: philosophy behind public domain?
Florian Weimer <[EMAIL PROTECTED]> writes: > * D. Richard Hipp: > >> Public domain just seemed the easiest way to go. > > It is, until you want to incorporate a contribution from someone who > can't give up his copyrught in a binding way. How do you handle > contributions from Europe, especially Germany? Or hasn't that > happened yet? > This is a point that always stroke me about "public domain": There is no such thing as "disclaiming copyright" in Europe (or at least Germany and Austria). Rotty -- Andreas Rottmann | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62 v2sw7MYChw5pr5OFma7u7Lw2m5g/l7Di6e6t5BSb7en6g3/5HZa2Xs6MSr1/2p7 hackerkey.com Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald E. Knuth
Re: [sqlite] 2 problems with sqlite3explorer.exe
Hello F.W.A. van Leeuwen, I have reason to believe that the the problem you describe might be present in my "SQLite Spy" (http://www.yunqa.de/delphi/sqlitespy/) as well, since the program is very similar to SQLite3 explorer. However, I was not able to reproduce the problem with SQLite3 Explorer in the first place. Could you describe it in a little more detail to get me going? Thanks, Ralf >2. I have a table with signed 32-bit integers. Doing queries with negative >values doesn't work. I have to specify the 2's complement value to get it >working.
RE: [sqlite] info
Reid Thompson wrote: > info apologies - i was trying to get the mailing list to give me a listing of available commands. Trying to suspend my subscription while out of the office. reid
[sqlite] info
info
Re: [sqlite] 2 problems with sqlite3explorer.exe
My previous post was not accurate. In fact, my data was unsigned, but sqlite3explorer DISPLAYS numbers > 2^31 as negative numbers. Maybe sqlite3explorer could use 64-bit integers to display numeric integer values. Best regards, Frank.
Re: [sqlite] Index with two columns
On Fri, 2005-06-03 at 13:20 +0200, Jakub Adamek wrote: > Hello, please, is there any way to make SQLite use an index on two > columns when I want to select all rows which have some combination of > the two columns? > > SELECT * FROM PointFeature WHERE > DsetId=203 AND SectId IN (4,400); > SQLite does use multiple columns of a multi-column index for == constraints. But for an IN operator, it will only using a single column. This is something that I need to work on. In the meantime, I suggest the following work-around: SELECT * FROM PointFeature WHERE DsetId=203 AND SectId=4 UNION ALL SELECT * FROM PointFeature WHERE DsetId=203 AND SectId=400; -- D. Richard Hipp <[EMAIL PROTECTED]>
[sqlite] 2 problems with sqlite3explorer.exe
To the author of sqlite3explorer: Thanks! It's a great tool!! I would like to support the tool by submitting 2 problems I've found: 1. The rowid (implicit column) is not displayed. 2. I have a table with signed 32-bit integers. Doing queries with negative values doesn't work. I have to specify the 2's complement value to get it working. Best regards, Frank.
Re: [sqlite] Porting SQLite to platform with no 64-bit integer support
Never mind, the native compiler DOES support 64-bit integers :-)
Re: [sqlite] Index with two columns
Jakub Adamek <[EMAIL PROTECTED]> writes: > Hello, please, is there any way to make SQLite use an index on two > columns when I want to select all rows which have some combination of > the two columns? > > My table is: > CREATE TABLE PointFeature ( > DSetId INTEGER, > SectId INTEGER, > PntItemId INTEGER); > > CREATE INDEX xxx ON PointFeature (DSetId, SectId, PntItemId); > > and the query is > SELECT * FROM PointFeature WHERE > DsetId=203 AND SectId IN (4,400); > > But the index is used just to find the DsetId and not to find SectId. > Is there another form of the SQL which could do that? Or do I have to > use two separate queries Try this instead: SELECT * FROM PointFeature WHERE DsetId=203 AND (SectId = 4 OR SectId = 400); Derrell
Re: [sqlite] Index with two columns
> Hello, please, is there any way to make SQLite use an index on two > columns when I want to select all rows which have some combination of > the two columns? > SELECT * FROM PointFeature WHERE > DsetId=203 AND SectId IN (4,400); I can't answer the question you asked, but I will point out one thing. Many SQL engines attempt to optimize index use in queries. For instance, in MS SQL Server, your query might *not* use the second column in the index if using the index would take perform more poorly than not using it. Using an index is not always faster than doing a table scan. If there are only a few rows where DsetId is equal to 203, the table scan of that subset could very well be faster than using an index to look up the values. In our MS SQL Server environment, we usually don't even bother to create indexes on more than one field if there are going to be less than a few hundred rows in a subset of a query like that. It takes the server longer to do the index lookup than it would the table scan.
[sqlite] Porting SQLite to platform with no 64-bit integer support
Hi, For a project I am working on, we'd like to use SQLite as an embedded database. The compiler we use for the platform (based on Analog Devices' Blackfin processor) does however not support 64-bit integers, which are used by SQLite. We have thought of three solutions (or workarounds) for this problem: 1. Compile in C++ mode and define a 64-bit integer class. This may have problems with dereferencing pointers to such numbers. 2. Redefine i64 as a 32-bit integer and hope they are not really needed (as long as the database file is < 2GByte). 3. Use the GNU compiler for Blackfin. However, we use a lot of software that is optimised (#pragmas) for Analog Devices' own compiler, so that would have to be re-done. Any advices? Best regards, Frank.
[sqlite] Lemon question
I'm using lemon to make a simple parser.I want to get more descriptive error messages. Right now, it prints Syntax error near '123'. Is there some way to make it print Syntax error near '123', expecting ';' or something similar? /Ludvig
[sqlite] Index with two columns
Hello, please, is there any way to make SQLite use an index on two columns when I want to select all rows which have some combination of the two columns? My table is: CREATE TABLE PointFeature ( DSetId INTEGER, SectId INTEGER, PntItemId INTEGER); CREATE INDEX xxx ON PointFeature (DSetId, SectId, PntItemId); and the query is SELECT * FROM PointFeature WHERE DsetId=203 AND SectId IN (4,400); But the index is used just to find the DsetId and not to find SectId. Is there another form of the SQL which could do that? Or do I have to use two separate queries SELECT * FROM PointFeature WHERE DsetId=203 AND SectId=4; SELECT * FROM PointFeature WHERE DsetId=203 AND SectId=400; Thank you very much, Jakub SELECT DsetId, SectId, pntitemid FROM add.point_features WHERE 1 AND DsetId=203 AND SectId IN (4,435) addropcode p1 p2 p3 0 Goto0 49 1 Integer 2 0 2 OpenRead1 66 keyinfo(3,BINARY,BINARY) 3 KeyAsData 1 1 4 SetNumColumns 1 4 5 Integer 203 0 6 NotNull -1 9 7 Pop 1 0 8 Goto0 47 9 MakeRecord 1 0 iii 10 MemStore0 0 11 MoveGe 1 47 12 MemLoad 0 0 13 IdxGE 1 47 + 14 RowKey 1 0 15 IdxIsNull 1 46 16 Integer 1 0 17 IfNot 1 46 18 MemLoad 1 0 19 If 0 32 20 Integer 1 0 21 MemStore1 1 22 OpenTemp2 0 keyinfo(1,BINARY) 23 SetNumColumns 2 1 24 Integer 4 0 25 MakeRecord 1 0 i 26 String8 0 0 27 PutStrKey 2 0 28 Integer 435 0 29 MakeRecord 1 0 i 30 String8 0 0 31 PutStrKey 2 0 32 Integer 1 0 33 Column 1 1 34 NotNull -1 38 35 Pop 2 0 36 String8 0 0 37 Goto0 41 38 MakeRecord 1 0 i 39 Found 2 41 40 AddImm -1 0 41 IfNot 1 46 42 Column 1 0 43 Column 1 1 44 Column 1 2 45 Callback3 0 46 Next1 12 47 Close 1 0 48 Halt0 0 49 Transaction 2 0 50 VerifyCookie2 79 51 Goto0 1 52 Noop0 0
Re: [sqlite] Large databases howto
Thanks for your answers. They seem encouraging. A few extra comments and questions: * We are doing tests for the active/daily (5M records) file with BEGIN END packages of 1000 inserts (with 2 indexes), and seems to be OK. We need also to do some queries/updates on this file (around 100K a day), but it seems that sqlite can cope with them. * ¿What about querying/updating the around 200 (6 months) historical data files (5M records each)? We know of the limitation to connecting to, at most, 32 files. ¿Any advice on improving the performance of querying such a huge database? * We are thinking on merging 7 daily files (5M records, with 2 indexes, each file) into one weekly file. ¿Which is the optimum way of doing this? Thanks again, Pedro Pascual Pedro Pascual wrote: Hi, We are evaluating using sqlite for a huge database: around 1000 millions records splitted into 200 files. Any experiences about this and tricks/howto's? The characteristics of our project: * The environment is a Unix box (IBM pSeries 64 bit) with fast (USCSI-3) disks. * No record deletes * Most of the (history) data will have a low update rate, and will be used mainly for queries. * Heavy inserts in active file (500 per day), closed every day (no more inserts) * Just two indexes on the data. Regards, Pedro Pascual
