Re: [sqlite] sqlite-3.7.6.1 coredump/hang

On 04/15/2011 05:35 PM, Thomas Klausner wrote: > On Fri, Apr 15, 2011 at 04:32:08PM +0700, Dan Kennedy wrote: >> How are you building sqlite3? Using configure/make from the >> sqlite-autoconf-3070601.tar.gz package on the website? > > Yes, using pkgsrc. What happens if you just try to build

Re: [sqlite] sqlite-3.7.6.1 coredump/hang

On Sat, Apr 16, 2011 at 01:48:16PM +0700, Dan Kennedy wrote: > What happens if you just try to build sqlite-autoconf-3070601.tar.gz > with "./configure && make"? That seems to work here with > "i386cd-5.1.iso" on a vm. wiz@yt:~/a/sqlite-autoconf-3070601> ./configure && make checking for a

[sqlite] sqlite-amalgamation + own functions = Segmentation fault at "sqlite3VdbeMemSetStr" sice version 3.7.5 (to v3.7.3 works fine)

Hello ! I hope you can understand my bad english ;-) Since a long time i use sqlite for my projects. Now i have updated from SQLite v3.7.3 over SQLite v3.7.5 to SQLite 3.7.6. I use SQLite Amalgamation and compile it with gcc 2.95 under windows xp. Compiling options for "Amalgamation" are :

[sqlite] 3.7.6.1 build error on platforms without pread/pwrite

It appears there is a bad check when setting up the pread (and pwrite) callback: #if defined(USE_PREAD) || defined(SQLITE_ENABLE_LOCKING_STYLE) { "pread",(sqlite3_syscall_ptr)pread, 0 }, #else { "pread",(sqlite3_syscall_ptr)0, 0 }, #endif SQLite forces

Re: [sqlite] sqlite-amalgamation + own functions = Segmentation fault at "sqlite3VdbeMemSetStr" sice version 3.7.5 (to v3.7.3 works fine)

Care to show us your SPL_mallocstr() function? Sounds like you've corrupted data if that line dies. All it's doing is checking an array value which is used all over the place in sqlite3.c If you put a break point there and on the first time it's hit put a watch on the address for

[sqlite] Newbie Question

My goal is to eventually become a contractor and work from home. It seems as if SQLite will optimally facilitate my goal—am I corect??  I will greatly appreciate any light that anyone can shed on this. ___ sqlite-users mailing list

Re: [sqlite] Newbie Question

On 16 Apr 2011, at 6:18pm, Db Dvlpr wrote: > My goal is to eventually become a contractor and work from home. It seems as > if > SQLite will optimally facilitate my goal—am I corect?? I will greatly > appreciate any light that anyone can shed on this. SQLite is a database tool, and allows

[sqlite] 'integer'

Hi, I ran into something I don't understand, maybe someone here can shed some light on it for me. I have a table named Tg which is created (with tcl) by: CREATE TABLE Tg (TgConfigId INTEGER PRIMARY KEY AUTOINCREMENT, OtherColumn INTEGER); If I do: INSERT INTO Tg (TgConfigId) VALUES

Re: [sqlite] 'integer'

http://www.sqlite.org/datatype3.html F. On Sat, Apr 16, 2011 at 7:40 PM, Tobias Vesterlund wrote: > Hi, > > I ran into something I don't understand, maybe someone here can shed some > light on it for me. > > I have a table named Tg which is created (with tcl)

Re: [sqlite] 'integer'

On 16 Apr 2011, at 6:40pm, Tobias Vesterlund wrote: > If I do: > INSERT INTO Tg (TgConfigId) VALUES (1); > > The following select works: > SELECT * FROM Tg WHERE TgConfigId = 1; > > But if I insert '1' instead I have to select on '1', 1 no longer works. That > makes some sense, but not

Re: [sqlite] Balance between keeping DBs open vs repeated open/close

At 18:11 06/04/2011, you wrote: >Thanks Stephan and Simon - I kind of figured it was one of those "how >long is a ball of string" questions, but I just wanted to check there >weren't any particular gotchas to watch out for. > >Regarding the separate files, it seems the best way to go. Each

[sqlite] Possible NATURAL JOIN bug

Sqlite 3.7.5. Possible NATURAL JOIN bug. I have a ~100 MB database which gives me odd results when running two similar queries. I'm currently trying to create a minimal test case, but the error seems to go away when I try to narrow it down. In short, the queries look like this (scrambled

Re: [sqlite] Newbie Question

Thanks, Simon. I wasn't getting that it's a tool. Thank you for the advice because as you know, I will need to be as marketable as possible. From: Simon Slavin To: General Discussion of SQLite Database Sent: Sat,

Re: [sqlite] sqlite-amalgamation + own functions = Segmentation fault at "sqlite3VdbeMemSetStr" sice version 3.7.5 (to v3.7.3 works fine)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/15/2011 06:28 AM, Jaromir Prinzler wrote: > I use SQLite Amalgamation and compile it with gcc 2.95 under windows xp. I strongly recommend you get a more recent version of the compiler. MinGW now has a decent automated installed and you'll get

[sqlite] SQLite 3.7.6 and 3.7.6.1 -- Performance issue with Triggers

Good afternoon, Here is an issue I started to experience after upgrading from SQLite 3.7.5 to 3.7.6 involving a trigger I have on a database table. The table with the trigger is a 2-column table with the following trigger installed to it: CREATE TABLE [table_a] ( [col_a] INTEGER NOT NULL

Re: [sqlite] SQLite 3.7.6 and 3.7.6.1 -- Performance issue with Triggers

On Sat, Apr 16, 2011 at 5:35 PM, Kenneth Ballard < kball...@kennethballard.com> wrote: > Good afternoon, > > Here is an issue I started to experience after upgrading from SQLite > 3.7.5 to 3.7.6 involving a trigger I have on a database table. > > The table with the trigger is a 2-column table

Re: [sqlite] SQLite 3.7.6 and 3.7.6.1 -- Performance issue with Triggers

On Sat, Apr 16, 2011 at 5:57 PM, Richard Hipp wrote: > > > On Sat, Apr 16, 2011 at 5:35 PM, Kenneth Ballard < > kball...@kennethballard.com> wrote: > >> Good afternoon, >> >> Here is an issue I started to experience after upgrading from SQLite >> 3.7.5 to 3.7.6 involving a

Re: [sqlite] SQLite 3.7.6 and 3.7.6.1 -- Performance issue with Triggers

The schema for these two tables is unchanged between the 3.7.5 and 3.7.6 version with the exception of the sort modifiers on table_b's unique index. Table table_b: CREATE TABLE [table_b] ( [col_a] INTEGER NOT NULL CONSTRAINT [fk_tableb_tablec] REFERENCES [tablec]([col_a]) ON DELETE CASCADE,

Re: [sqlite] 'integer'

On Sat, Apr 16, 2011 at 07:40:59PM +0200, Tobias Vesterlund scratched on the wall: > Hi, > > I ran into something I don't understand, maybe someone here can shed some > light on it for me. > > I have a table named Tg which is created (with tcl) by: > > CREATE TABLE Tg (TgConfigId INTEGER

Re: [sqlite] Balance between keeping DBs open vs repeated open/close

> Keep in mind that sqlite has a limit of 32 open databases. 32 _attached_ databases, not opened. With different sqlite3* handlers you can open as many databases as you want (and your memory permits). Pavel On Thu, Apr 7, 2011 at 6:05 AM, Eduardo wrote: > At 18:11

Re: [sqlite] SQLite 3.7.6 and 3.7.6.1 -- Performance issue with Triggers

On Sat, Apr 16, 2011 at 6:29 PM, Kenneth Ballard < kball...@kennethballard.com> wrote: > The schema for these two tables is unchanged between the 3.7.5 and 3.7.6 > version with the exception of the sort modifiers on table_b's unique index. > Using the schema and sqlite_stat1 data you provide, I