On Oct 16, 2009, at 2:53 PM, Vladimir Looze wrote:
> Sqlite causes Segmentation fault on SQL insert.
>
> Steps to reproduce:
> 1. create database with following schema (table/column names dosen't
> matter)
>
> ----- BEGIN OF SQL LISTING
> create table tname ( id integer not null primary key asc
> autoincrement,
> cname string );
> create table surname ( id integer not null primary key asc
> autoincrement,
> surname string );
> create table people ( cname integer not null references cname (id),
> surname integer not null references surnname (id));
> create view peopleview as
> select tname.cname, surname.surname from people
> left outer join tname on (tname.id = people.cname)
> left outer join surname on (surname.id = people.surname);
>
> create trigger create_people instead of insert on peopleview
> begin
> insert into tname (cname) values (new.cname);
> insert into surname (surname) values (new.surname);
> end;
> ----- END OF SQL LISTING
>
> 2. execute sql insert statement: insert into peopleview
> values('John', 'Smith');
Thanks for the report. Looks like the same bug as this one:
http://www.sqlite.org/src/info/a696379c1f088
Was fixed for 3.6.19.
Dan.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
