your solution is only for one row as opposed to my example creating many rows
On Wed, 2 Aug 2017 at 18:27, Peter Da Silva <peter.dasi...@flightaware.com> wrote: > By “the same thing” I mean: > > BEGIN; > something like the stuff I had in my original post where it’s incrementing > the sequence; > your statement where you’re using the sequence, except using something > like (SELECT value FROM super_sequences WHERE id=’SEQ_1’); > COMMIT; > > On 8/2/17, 11:20 AM, "sqlite-users on behalf of Sylvain Pointeau" < > sqlite-users-boun...@mailinglists.sqlite.org on behalf of > sylvain.point...@gmail.com> wrote: > > On Wed, Aug 2, 2017 at 5:54 PM, Peter Da Silva < > peter.dasi...@flightaware.com> wrote: > > > Can’t you do the same basic logic then use (SELECT value FROM > > super_sequences WHERE id=’SEQ_1’) instead of SEQ_1.nextval? > > > > > > insert into mytable (MY_NO, MY_INFO) > > SELECT SEQ_1.nextval, a.INFO FROM myothertable a > > ; > > > > > no because nextval also increment the sequence, as opposed to the > (SELECT > value FROM super_sequences WHERE id=’SEQ_1’) where it only reads the > value > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
