Probably best reserved for initialization of a shard of a database where
you can set next to last of a prior .db.
On Tue, Jan 30, 2018 at 9:14 AM, petern wrote:
> For one, within a function that does an INSERT, set_last_insert_rowid makes
> it possible to "pop" last_insert_rowid.
> Consider a f
I don't need this program so delete this.
Sent from Yahoo Mail on Android
On Tue, Jan 30, 2018 at 11:15 AM, petern wrote:
For one, within a function that does an INSERT, set_last_insert_rowid makes
it possible to "pop" last_insert_rowid.
Consider a function which INSERT's into the model an
For one, within a function that does an INSERT, set_last_insert_rowid makes
it possible to "pop" last_insert_rowid.
Consider a function which INSERT's into the model and then INSERT's a log
table row. The caller probably isn't interested in the log rowid.
A better question to ask is always why an
Just wonder what the possible use for this is.
RBS
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 6 Mar 2017, at 10:01pm, Richard Hipp wrote:
> On 3/6/17, Simon Slavin wrote:
>>
>> This means that each TRIGGER is its own little story, right ? Triggers can
>> make their own inserts. Which may themselves have triggers. SQLite
>> maintains a happy stack of values for last_insert_rowid()
On 3/6/17, Simon Slavin wrote:
>
> This means that each TRIGGER is its own little story, right ? Triggers can
> make their own inserts. Which may themselves have triggers. SQLite
> maintains a happy stack of values for last_insert_rowid(), pushing and
> popping them each time you enter or exit
On 6 Mar 2017, at 9:30pm, Richard Hipp wrote:
>https://www.sqlite.org/draft/releaselog/3_18_0.html <--- Change log
The mention of sqlite3_set_last_insert_rowid() reminds me of a question I have:
Here’s the documentation for last_insert_rowid():
"If an INSERT occurs within a trigger or w
7 matches
Mail list logo
