[sqlite] [3.6.2] make test errors
I don't know, if it's really needed by community. But I got this erros by "make test" on x86_64-pc-linux-gnu platform: 12 errors out of 23377 tests Failures on these tests: lookaside-1.4 lookaside-1.5 memsubsys1-2.3 memsubsys1-2.4 memsubsys1-3.2.4 memsubsys1-4.3 memsubsys1-4.4 memsubsys1-5.3 memsubsys1-6.3 memsubsys1-6.4 memsubsys1-7.4 memsubsys1-7.5 Unfreed memory: 1080 bytes Writing unfreed memory log to "./memleak.txt" Memory used: now 1080 max 112168 max-size4128768 Page-cache used: now 0 max 0 max-size 4096 Page-cache overflow: now 0 max3258200 Scratch memory used: now 0 max 0 Scratch overflow: now 0 max 33320 max-size 33320 Maximum memory usage: 112168 bytes Current memory usage: 1080 bytes Number of malloc() : -1 calls make: *** [test] Error 1 -- Alexander Batyrshin aka bash bash = Biomechanica Artificial Sabotage Humanoid ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] DBD::SQLite::Amalgamation-3.6.1.2 FTS3 seg faulting... solution... upgrade code
I mean what is benefits of using DBD::SQLite::Amalgamation? Where it can be needed? -- Alexander Batyrshin aka bash bash = Biomechanica Artificial Sabotage Humanoid On Sun, Sep 21, 2008 at 9:51 AM, P Kishor <[EMAIL PROTECTED]> wrote: > On 9/21/08, Alexander Batyrshin <[EMAIL PROTECTED]> wrote: >> Sorry for off-topic. >> What is main difference between DBD::SQLite and DBD::SQLite::Amalgamation? > > Exactly what it says on the box. The latter uses the SQLite > amalgamation. The former doesn't. They both work exactly the same for > the end user. > > >> -- >> Alexander Batyrshin aka bash >> bash = Biomechanica Artificial Sabotage Humanoid >> >> >> >> >> On Sat, Sep 20, 2008 at 8:04 PM, P Kishor <[EMAIL PROTECTED]> wrote: >> > I encountered this problem and solved it, so hopefully this will help >> > some other poor sod. >> > >> > Audrey Tang's otherwise most excellent DBD::SQLite::Amalgamation >> > (bless her for this incredible package) was causing segmentation >> > faults for me while doing FTS3 searches on a RH ES3 Linux box. The >> > package version 3.6.1.2 has code for SQLite 3.6.1. >> > >> > I upgraded the code in the package to SQLite 3.6.2 (just copied the >> > corresponding files from the SQLite tarball... one file had to be >> > renamed from sqlite.c to sqlite-amalgamation.c) and rebuilt the DBD. >> > Everything is now fine in happy town. >> > >> > -- >> > Puneet Kishor >> >> > ___ >> > sqlite-users mailing list >> > sqlite-users@sqlite.org >> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > >> > > > -- > Puneet Kishor http://punkish.eidesis.org/ > Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ > Open Source Geospatial Foundation (OSGeo) http://www.osgeo.org/ > ___ > 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] DBD::SQLite::Amalgamation-3.6.1.2 FTS3 seg faulting... solution... upgrade code
On 9/21/08, Alexander Batyrshin <[EMAIL PROTECTED]> wrote: > Sorry for off-topic. > What is main difference between DBD::SQLite and DBD::SQLite::Amalgamation? Exactly what it says on the box. The latter uses the SQLite amalgamation. The former doesn't. They both work exactly the same for the end user. > -- > Alexander Batyrshin aka bash > bash = Biomechanica Artificial Sabotage Humanoid > > > > > On Sat, Sep 20, 2008 at 8:04 PM, P Kishor <[EMAIL PROTECTED]> wrote: > > I encountered this problem and solved it, so hopefully this will help > > some other poor sod. > > > > Audrey Tang's otherwise most excellent DBD::SQLite::Amalgamation > > (bless her for this incredible package) was causing segmentation > > faults for me while doing FTS3 searches on a RH ES3 Linux box. The > > package version 3.6.1.2 has code for SQLite 3.6.1. > > > > I upgraded the code in the package to SQLite 3.6.2 (just copied the > > corresponding files from the SQLite tarball... one file had to be > > renamed from sqlite.c to sqlite-amalgamation.c) and rebuilt the DBD. > > Everything is now fine in happy town. > > > > -- > > Puneet Kishor > > > ___ > > sqlite-users mailing list > > sqlite-users@sqlite.org > > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > -- Puneet Kishor http://punkish.eidesis.org/ Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ Open Source Geospatial Foundation (OSGeo) http://www.osgeo.org/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] DBD::SQLite::Amalgamation-3.6.1.2 FTS3 seg faulting... solution... upgrade code
Sorry for off-topic. What is main difference between DBD::SQLite and DBD::SQLite::Amalgamation? -- Alexander Batyrshin aka bash bash = Biomechanica Artificial Sabotage Humanoid On Sat, Sep 20, 2008 at 8:04 PM, P Kishor <[EMAIL PROTECTED]> wrote: > I encountered this problem and solved it, so hopefully this will help > some other poor sod. > > Audrey Tang's otherwise most excellent DBD::SQLite::Amalgamation > (bless her for this incredible package) was causing segmentation > faults for me while doing FTS3 searches on a RH ES3 Linux box. The > package version 3.6.1.2 has code for SQLite 3.6.1. > > I upgraded the code in the package to SQLite 3.6.2 (just copied the > corresponding files from the SQLite tarball... one file had to be > renamed from sqlite.c to sqlite-amalgamation.c) and rebuilt the DBD. > Everything is now fine in happy town. > > -- > Puneet Kishor > ___ > 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] inconsistent .dump output
Howdy folks, I've been trying to test some cross compatability of sqlite, and having a heck of a time with sqlites database .dumps and MiXeD CaSe based schemas. The problem stems from an odd behavior of .dump to not quote identifiers when outputting DDL, but to then quote the identifiers when outputting the DML. (Is this really the desired behavior? I can't think of any reason you would want it to work like this) This works ok for dumps going back into sqlite, however it doesn't work with other database systems, which attempt to casefold the schema, but then attempt to load data using the non-case-folded table names given in the insert statements. I think the ideal solution would probably be to have an option to switch between consistently quoteing or unquoteing (I can think of use cases for both methods), is there any chance something like that could be implemented? In the mean time, I'm wondering if anyone can think of another work around for this? TIA. -- Robert Treat brighterlamp.org ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] .import multi-line record from a text file to a table
On 9/20/08, Qianqian Fang <[EMAIL PROTECTED]> wrote: > excellent! this works for me. > thank you very much! > > > Qianqian > > > Kees Nuyt wrote: > > You will have to transform the XML into an INSERT statement, > > like this: > > > > INSERT INTO final (idx,enc,data) VALUES ('rec1','001','line1 > > line2 > > line3'); > > > > Going back to your original question Qiangian... unfortunately, it seems the CSV .import mechanism can't handly line breaks in records (someone please correct me if I am wrong). I created a table like so and added a record to it sqlite> CREATE TABLE foo (a, b, c); sqlite> INSERT INTO foo VALUES (1, '001', 'line1 ...> line2 ...> line3'); sqlite> SELECT * FROM foo; 1|001|line1 line2 line3 sqlite> .m csv sqlite> .sep "|" sqlite> .o foo.txt sqlite> SELECT * FROM foo; sqlite> meanwhile, back in the shell % less foo.txt 1|001|"line1 line2 line3" % back in sqlite3 sqlite> .import foo.txt foo foo.txt line 2: expected 3 columns of data but found 1 sqlite> -- Puneet Kishor http://punkish.eidesis.org/ Nelson Institute for Environmental Studies http://www.nelson.wisc.edu/ Open Source Geospatial Foundation (OSGeo) http://www.osgeo.org/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] VACUUM trouble
OK, the mystery has been solved: didn't notice, that disk just reached 100% usage... :D -- pozdrawiam / regards Zbigniew Baniewski ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] VACUUM trouble
On Sun, Sep 21, 2008 at 12:26:32AM +0100, [EMAIL PROTECTED] wrote: > You know what disk IO error means, right? Run scandisk No, the disk is OK. > and try dumping the database and restoring it to a new file. Yes, I'm aware, that one can just create the database anew - but I was asking, why VACUUM is giving up. No, it's not hardware-related trouble. Meanwhile I've found something related: http://www.mail-archive.com/sqlite-users@sqlite.org/msg24905.html Is it filesystem-related problem? Is it possible, that SQLite just "doesn't like" Reiserfs? -- pozdrawiam / regards Zbigniew Baniewski ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] VACUUM trouble
A 25mb file is nothing for SQLite; I vacuumed a 270mb test database a few hours ago with no problems. You know what disk IO error means, right? Run scandisk and try dumping the database and restoring it to a new file. On 9/21/08, Zbigniew Baniewski <[EMAIL PROTECTED]> wrote: > It seems, it's not possible to VACUUM a bit larger file? I tried to VACUUM > a database file of 25 MB size, containing 75000 records (about 20 fields > each). Unfortunately, each VACUUM attempt is interrupted with message: > > SQL error: disk I/O error > > No VACUUM allowed for such size? > > Linux 2.6.26, SQLite 3.6.1, 256 MB RAM > -- > pozdrawiam / regards > > Zbigniew Baniewski > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Seun Osewa http://www.nairaland.com/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] VACUUM trouble
It seems, it's not possible to VACUUM a bit larger file? I tried to VACUUM a database file of 25 MB size, containing 75000 records (about 20 fields each). Unfortunately, each VACUUM attempt is interrupted with message: SQL error: disk I/O error No VACUUM allowed for such size? Linux 2.6.26, SQLite 3.6.1, 256 MB RAM -- pozdrawiam / regards Zbigniew Baniewski ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] .import multi-line record from a text file to a table
excellent! this works for me. thank you very much! Qianqian Kees Nuyt wrote: > You will have to transform the XML into an INSERT statement, > like this: > > INSERT INTO final (idx,enc,data) VALUES ('rec1','001','line1 > line2 > line3'); > ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Simple Suggestions
ivo welch wrote: > * SHOW columns FROM table--- would be a great addition, if only > for compatibility with MySQL. Aside, it is easier to remember than a > pragma. MySQL's SHOW features are just an old MySQL-proprietary way of doing introspection, prior to their adding support for the SQL standard INFORMATION_SCHEMA. If SQLite is going to add any introspection features for compatability with other DBMSs, it should go the information schema route, or in SQLite terms, information database. -- Darren Duncan ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Simple Suggestions
"ivo welch" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > * Two simple functions would make SQLite much more useful to me are: Be aware that you can extend SQLite with custom functions. See sqlite3_create_function[16] Igor Tandetnik ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Between And statement too much slow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > The EXPLAIN QUERY PLAN keyword works, and I love it, but it's > completely undocumented. How come? http://www.sqlite.org/cvstrac/wiki?p=QueryPlans Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFI1U12mOOfHg372QQRAgQMAJ9JwWzSeVv3D9IifYCV8c3GmK1/ZACeIB7g WwultGFCfDcoZ+d2p3JYotQ= =egjX -END PGP SIGNATURE- ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] .import multi-line record from a text file to a table
On Sat, 20 Sep 2008 10:58:25 -0400, Qianqian wrote: > hi > > I am quite new to sqlite, so, please forgive me if there > is anything obviously incorrect. > > I created a table with the following fields: > >create table final(idx varchar(10), enc varchar(8), data varchar(4096)); > >and I want to import the following xml-type of data to this table: > >rec1 >001 > >line 1 >line 2 >line 3 > > > I noticed that load_file() function does not work in sqlite, > but sqlite has .import command. > So, I reformatted the xml into the following > >rec1|001|line1 >line2 >line3 > > and import it using the following command > >.separator "|" >.import recdata.txt final > > sqlite complained about "recdata.txt line 2: > expected 3 columns of data but found 1" The .import command is very basic and doesn't support this. > my question is: is there a way I can import fields with > multiple lines to sqlite? You will have to transform the XML into an INSERT statement, like this: INSERT INTO final (idx,enc,data) VALUES ('rec1','001','line1 line2 line3'); >is importing xml supported in sqlite >(I did not see it from the documentation)? No, it isn't. Perhaps Tcl can do it, or xgawk. > thank you > > Qianqian -- ( Kees Nuyt ) c[_] ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Simple Suggestions
ivo welch wrote: > Sqlite is a wonderful program. A big thanks to its creator. As a new > user, the following are nuisances, though, so I thought I would > register these as simple suggestions: > > * SHOW columns FROM table--- would be a great addition, if only > for compatibility with MySQL. Aside, it is easier to remember than a > pragma. This is done pretty easily. With sqlite3 do a .schema and it will tell you what tables are in the database, as well as the command used to create them. > * Two simple functions would make SQLite much more useful to me are: > > [1] the simple logarithm function "log" or "ln" (which would make a > power function easy), > > [2] the aggregate function "standard deviation" (which together with > the average may well be the most commonly used statistical function). > > > * sqlitebrowser is very buggy under linux when it comes to importing > csv files. often, nothing happens. sometimes, trying a second import > works. just buggy. > > > These should all be trivially easy to add (I hope). A more complex > request would be to build an "import csv file" functionality into > sqlite itself, but this could have other negative consequences. sqlitebrowser is not authored by the sqlite people, so if it doesn't work you should report it to them. Sqlite3 does have a .import option that works for CSV files great. I've used it several times and it works great. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Simple Suggestions
Sqlite is a wonderful program. A big thanks to its creator. As a new user, the following are nuisances, though, so I thought I would register these as simple suggestions: * SHOW columns FROM table--- would be a great addition, if only for compatibility with MySQL. Aside, it is easier to remember than a pragma. * Two simple functions would make SQLite much more useful to me are: [1] the simple logarithm function "log" or "ln" (which would make a power function easy), [2] the aggregate function "standard deviation" (which together with the average may well be the most commonly used statistical function). * sqlitebrowser is very buggy under linux when it comes to importing csv files. often, nothing happens. sometimes, trying a second import works. just buggy. These should all be trivially easy to add (I hope). A more complex request would be to build an "import csv file" functionality into sqlite itself, but this could have other negative consequences. thanks again, /iaw ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] Disabling index [was Re: Performance/bug in multikey 'group by' in 3.6.2
Alternatively: pragma planner_ignore_index=1 On Sep 20, 2008, at 11:37 AM, Russell Leighton <[EMAIL PROTECTED] > wrote: > It would be very nice to have a way to explicitly control index use. > > I'm going to test my theory this weekend but I think if the index is > not cached and the data large then the group by is faster without the > index. If this is the case I have a real issue. I need the index for > other queries and can't afford to drop it for the aggregations. I just > want to tell the query planner to not use any index. > > If there is no way to do this with the current parser could we have an > extension to select? Maybe something like: >select with no index >select with index index1,index2 > > Thoughts? > > > On Sep 20, 2008, at 10:33 AM, "Jay A. Kreibich" <[EMAIL PROTECTED]> wrote: > >> On Fri, Sep 19, 2008 at 10:47:33PM -0400, Russ Leighton scratched on >> the wall: >> >>> What about the null values for the aggregation keys when I put a '+' >>> to disable the index? Is that 'as designed'? >> >> The "+" operator gets rid of type-affinities, and that can lead to >> unexpected results. I'm not sure if one would consider these >> specific results "as designed" or not, but it is known that "+" is >> not totally without side effects: >> >> http://www.sqlite.org/cvstrac/tktview?tn=3279 >> >> >> -j >> >> >> -- >> Jay A. Kreibich < J A Y @ K R E I B I.C H > >> >> "Our opponent is an alien starship packed with atomic bombs. We have >> a protractor." "I'll go home and see if I can scrounge up a ruler >> and a piece of string." --from Anathem by Neal Stephenson >> ___ >> 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-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] .import multi-line record from a text file to a table
hi I am quite new to sqlite, so, please forgive me if there is anything obviously incorrect. I created a table with the following fields: >>create table final(idx varchar(10), enc varchar(8), data varchar(4096)); and I want to import the following xml-type of data to this table: rec1 001 line 1 line 2 line 3 I noticed that load_file() function does not work in sqlite, but sqlite has .import command. So, I reformatted the xml into the following rec1|001|line1 line2 line3 and import it using the following command >>.separator "|" >>.import recdata.txt final sqlite complained about "recdata.txt line 2: expected 3 columns of data but found 1" my question is: is there a way I can import fields with multiple lines to sqlite? is importing xml supported in sqlite (I did not see it from the documentation)? thank you Qianqian ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] DBD::SQLite::Amalgamation-3.6.1.2 FTS3 seg faulting... solution... upgrade code
I encountered this problem and solved it, so hopefully this will help some other poor sod. Audrey Tang's otherwise most excellent DBD::SQLite::Amalgamation (bless her for this incredible package) was causing segmentation faults for me while doing FTS3 searches on a RH ES3 Linux box. The package version 3.6.1.2 has code for SQLite 3.6.1. I upgraded the code in the package to SQLite 3.6.2 (just copied the corresponding files from the SQLite tarball... one file had to be renamed from sqlite.c to sqlite-amalgamation.c) and rebuilt the DBD. Everything is now fine in happy town. -- Puneet Kishor ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Performance/bug in multikey 'group by' in 3.6.2
It would be very nice to have a way to explicitly control index use. I'm going to test my theory this weekend but I think if the index is not cached and the data large then the group by is faster without the index. If this is the case I have a real issue. I need the index for other queries and can't afford to drop it for the aggregations. I just want to tell the query planner to not use any index. If there is no way to do this with the current parser could we have an extension to select? Maybe something like: select with no index select with index index1,index2 Thoughts? On Sep 20, 2008, at 10:33 AM, "Jay A. Kreibich" <[EMAIL PROTECTED]> wrote: > On Fri, Sep 19, 2008 at 10:47:33PM -0400, Russ Leighton scratched on > the wall: > >> What about the null values for the aggregation keys when I put a '+' >> to disable the index? Is that 'as designed'? > > The "+" operator gets rid of type-affinities, and that can lead to > unexpected results. I'm not sure if one would consider these > specific results "as designed" or not, but it is known that "+" is > not totally without side effects: > > http://www.sqlite.org/cvstrac/tktview?tn=3279 > > > -j > > > -- > Jay A. Kreibich < J A Y @ K R E I B I.C H > > > "Our opponent is an alien starship packed with atomic bombs. We have > a protractor." "I'll go home and see if I can scrounge up a ruler > and a piece of string." --from Anathem by Neal Stephenson > ___ > 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] How to convert any dataType to sqlite3_value ?
"suku249" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Igor Tandetnik wrote: >> >> suku249 <[EMAIL PROTECTED]> >> wrote: >>> I need to convert dataTypes like int or string into sqlite3_value. >> >> Why? What are you trying to achieve? > > We are trying to implement fts3 functionality without using the > virtual table implementation, So we are trying to implement three > functionalities, createTable(creates content,segement and seg dir > table), InsertData (insert data into the 3 tables) and selectTerms ( > which selects data from 3 tables). These functions will be directly > called from client apps. For this, we are trying to port code from > fts3.c. Data content is passed as type sqlite3_value in many > functions in fts3.c. To port existing functionalities in fts3.c, we > need to use sqlite3_value. Well, there's no public API to create these structures. Since you are deep in SQLite source code anyway, I guess you could extract necessary functionality from it. However, I would imagine that the first thing those FTS3 functions do is extract actual values from sqlite3_value structures. Couldn't you just strip that part from the code, and make your functions take the strongly-typed values directly? That should make both your and your clients' lives easier. Igor Tandetnik ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] LiquiBase now supports SQLite
I just wanted to point out that LiquiBase now supports SQLite. LiquiBase is an LGPL Java-based tool for managing and applying database changes. The general idea is that you specify each change you need applied to your database in a file and each time you update the database based on that file, the applied changes are recorded in the database. t is similar to Ruby's ActiveMigrations, but tracks each change independently rather than having a "database version" and so it works much better with multiple developers and multiple code branches. LiquiBase supports many advanced functionality such as the ability to roll back changes, preconditions, change contexts, database "diffs", documentation generation, and more. For more information, see http://www.liquibase.org/home. If you have any questions or issues, be sure to let us know. Nathan ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] .import multi-line record from a text file to a table
hi I am quite new to sqlite, so, please forgive me if there is anything obviously incorrect. I created a table with the following fields: >>create table final(idx varchar(10), enc varchar(8), data varchar(4096)); and I want to import the following xml-type of data to this table: rec1 001 line 1 line 2 line 3 I noticed that load_file() function does not work in sqlite, but sqlite has .import command. So, I reformatted the xml into the following rec1|001|line1 line2 line3 and import it using the following command >>.separator "|" >>.import recdata.txt final sqlite complained about "recdata.txt line 2: expected 3 columns of data but found 1" my question is: is there a way I can import fields with multiple lines to sqlite? is importing xml supported in sqlite (I did not see it from the documentation)? thank you Qianqian ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Performance/bug in multikey 'group by' in 3.6.2
On Fri, Sep 19, 2008 at 10:47:33PM -0400, Russ Leighton scratched on the wall: > What about the null values for the aggregation keys when I put a '+' > to disable the index? Is that 'as designed'? The "+" operator gets rid of type-affinities, and that can lead to unexpected results. I'm not sure if one would consider these specific results "as designed" or not, but it is known that "+" is not totally without side effects: http://www.sqlite.org/cvstrac/tktview?tn=3279 -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our opponent is an alien starship packed with atomic bombs. We have a protractor." "I'll go home and see if I can scrounge up a ruler and a piece of string." --from Anathem by Neal Stephenson ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Between And statement too much slow
The EXPLAIN QUERY PLAN keyword works, and I love it, but it's completely undocumented. How come? On 9/19/08, Stephen Oberholtzer <[EMAIL PROTECTED]> wrote: > On Fri, Sep 19, 2008 at 12:36 PM, Giuseppe Costanzi > <[EMAIL PROTECTED]>wrote: > >> >> How could improve my code? > > > Go into the sqlite3 command line and issue > > EXPLAIN QUERY PLAN > > You'll have to fill in some values for the ?s, but that'll give you some > hints. > > > Also: How long is "too slow"? Several seconds? > > > -- > -- Stevie-O > Real programmers use COPY CON PROGRAM.EXE > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Seun Osewa http://www.nairaland.com/ ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] JOIN works very strange [3.6.2]
On Sat, Sep 20, 2008 at 08:45:16AM +0400, Alexander Batyrshin scratched on the wall: > Hello everyone, > > I gets strange result from this query on SQLite-3.6.2 > > SELECT > town.id, town_log.new_player_id, player.name > FROM > town_log > LEFT JOIN town > LEFT JOIN player > ON > town.id = town_log.town_id AND town_log.new_player_id = player.id > WHERE > town_log.id = 5195 "ON" is part of a JOIN operation. You have two JOINs but only one ON, and it is only getting applied to the second JOIN. I think you want something closer to this: ... FROM town_log LEFT JOIN town ON town.id = town_log.town_id LEFT JOIN player ON town_log.new_player_id = player.id WHERE town_log.id = 5195 -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our opponent is an alien starship packed with atomic bombs. We have a protractor." "I'll go home and see if I can scrounge up a ruler and a piece of string." --from Anathem by Neal Stephenson ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] How to convert any dataType to sqlite3_value ?
We are trying to implement fts3 functionality without using the virtual table implementation, So we are trying to implement three functionalities, createTable(creates content,segement and seg dir table), InsertData (insert data into the 3 tables) and selectTerms ( which selects data from 3 tables). These functions will be directly called from client apps. For this, we are trying to port code from fts3.c. Data content is passed as type sqlite3_value in many functions in fts3.c. To port existing functionalities in fts3.c, we need to use sqlite3_value. Igor Tandetnik wrote: > > suku249 <[EMAIL PROTECTED]> > wrote: >> I need to convert dataTypes like int or string into sqlite3_value. > > Why? What are you trying to achieve? > > Igor Tandetnik > > > > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > -- View this message in context: http://www.nabble.com/How-to-convert-any-dataType-to-sqlite3_value---tp19574177p19584357.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users