Can’t you do the same basic logic then use (SELECT value FROM super_sequences
WHERE id=’SEQ_1’) instead of SEQ_1.nextval?
On 8/2/17, 10:48 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:43 PM, Peter Da Silva <
peter.dasi...@flightaware.com> wrote:
> Hence the suggestion to script a transaction. For example, in pseudocode:
>
> BEGIN;
> SELECT value, increment from super_sequences where table = :table and
> column = :column;
> INSERT INTO :table (id, other, fields) VALUES :(value+increment,other,
> values);
> UPDATE super_sequences set value = :(value + increment) WHERE table =
> :table and column = :column;
> COMMIT;
>
ok but it does not work for insert like
insert into mytable (MY_NO, MY_INFO)
SELECT SEQ_1.nextval, a.INFO FROM myothertable a
;
_______________________________________________
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
