On Apr 13, 2017, at 2:36 AM, Dominique Devienne wrote:
> On Thu, Apr 13, 2017 at 6:18 AM, Guy Harris wrote:
>
>> Here's a patch, against the current Fossil repository, including some
>> changes we've made to lemon.c in Wireshark, that gets rid of old-style K&R
>> function definitions/declaratio
On 13 Apr 2017, at 6:51pm, Keith Medcalf wrote:
> The only real problem I see with SQLite3's implementation of SAVEPOINT is
> that if you issue SAVEPOINT outside of a transaction (ie, when in autocommit
> mode) it should throw an error, not start a transaction for you.
A question on this list
Olivier,
However, this is unique to SQLite. In "just about any other" database software
you have to know whether you are in a transaction or not, because you *CANNOT*
request/release/rollback a savepoint outside of a transaction. It just happens
that SQLite runs each "statement" inside a tra
Thanks Keith for your followup, I see my answer to Clemens helped focus what
I'm on. :)
> Le 13 avr. 2017 à 16:11, Keith Medcalf a écrit :
>
> You use the sqlite3_autocommit() to determine if you are in "magical" mode or
> inside a transaction.
Hmm. I failed to spot sqlite3_get_autocommit()
In a very large program, made of a lot of 'subsystems', some methods might have
to do some read and update work, sometimes being called from contexts where
there already is an OUTER transaction open, and sometimes being called with no
OUTER transactions open.
If I could be satisfied with a DEFE
On 13 Apr 2017, at 2:39pm, Olivier Mascia wrote:
> Known, but thanks. :)
> The question was why SAVEPOINT, when there is no outer transaction, is
> limited to the behavior of simple BEGIN (which is BEGIN DEFERRED) and does
> not offer provision for IMMEDIATE or EXCLUSIVE mode (I'm only interes
The traditional use of SAVEPOINT is to save a spot "inside" a transaction.
Almost all other implementations of SQL REQUIRE a transaction to already be in
progress before you can create a savepoint (which makes total sense -- how can
you save the state of something which does not exist?). SQLi
On 4/13/17, Keith Medcalf wrote:
>
> So in the case of
> SQLite just using the standard shell compiled without authorization hooks in
> place is sufficient to do what you will to the database
Yes. The sqlite3_set_authorizer() feature is designed to allow a
restricted subset of SQL to be used in
Clemens,
Friendly said, you might have missed my point, which probably simply
demonstrate I failed stating it correctly.
> Le 13 avr. 2017 à 14:14, Clemens Ladisch a écrit :
>
> Olivier Mascia wrote:
>> "When a SAVEPOINT is the outer-most savepoint and it is not within
>> a BEGIN...COMMIT then
On Thursday, 13 April, 2017 06:14, Matthias-Christian Ott
wrote:
> I'm unsure what the threat and security model of SQLite's authorizer
> callback is. I think it would only be an effective authorization
> mechanism if the attacker was able to only execute SQL statements on a
> database and the
On 4/13/17, Matthias-Christian Ott wrote:
>
> It seems it is not possible to call sqlite3_db_config from SQL,
Exactly. And since the programmers who implement the authorizer
callback know whether or not the database name has changed, they know
whether or not to check for "main" or some other nam
I'm unsure what the threat and security model of SQLite's authorizer
callback is. I think it would only be an effective authorization
mechanism if the attacker was able to only execute SQL statements on a
database and the database was otherwise not accessible to the attacker.
So I'm not sure whethe
Olivier Mascia wrote:
> "When a SAVEPOINT is the outer-most savepoint and it is not within
> a BEGIN...COMMIT then the behavior is the same as BEGIN DEFERRED
> TRANSACTION."
>
> What are the specific reasons for SAVEPOINT to be limited to BEGIN
> DEFERRED in that case?
A BEGIN without a type is DE
-Original Message-
From: no...@null.net
What would be useful (at least via the shell CLI) is a "list_pragmas"
pragma that shows for example something like this:
sqlite> PRAGMA list_pragmas;
PRAGMA list;
would be less redundant.
___
sqli
On Thu, Apr 13, 2017 at 6:18 AM, Guy Harris wrote:
> Here's a patch, against the current Fossil repository, including some
> changes we've made to lemon.c in Wireshark, that gets rid of old-style K&R
> function definitions/declarations, and also removes trailing white space
> from some lines (the
Dear all and SQLite Developers,
About: https://www.sqlite.org/lang_savepoint.html
"The SAVEPOINT command starts a new transaction with a name. The transaction
names need not be unique. A SAVEPOINT can be started either within or outside
of a BEGIN...COMMIT. When a SAVEPOINT is the outer-most
On Wed Apr 12, 2017 at 03:38:11PM -0400, Richard Hipp wrote:
> On 4/12/17, Jens Alfke wrote:
> > Many of SQLite's pragma commands change database settings. It would be
> > helpful if their documentation[1] stated which of these persist across
> > closing/reopening the database, and which are scope
17 matches
Mail list logo
