> > in some cases the SIndex captured inside the first lambda
> > (UPDATE statement) appeared to be null even though it wasn't null in the
> > enclosing scope (setVersion_)
>
> Interesting (and disturbing) result. Is this with Oracle's java compiler?
>
Compiler is Oracle JDK 8u40-b25 on OSX
On Wed, Sep 23, 2015 at 12:00 AM, Rowan Worth wrote:
> > SIndex sidx is just a boxed immutable integer.
>
> If it were me I'd be reviewing this assumption very carefully. The sequence
> of events:
>
public class SIndex {
private final int _i;
public SIndex(int i) {
_i = i;
}
public int
Not important.
On Tue, Sep 22, 2015 at 6:00 PM, Simon Slavin wrote:
>
> On 22 Sep 2015, at 5:40am, Hugues Bruant wrote:
>
> > Forgot to include the db in the previous email.
>
> You can't attach files to messages in this list. If it's important,
> please post the fi
>
> That does look a bit like magic - and as is 99.9% the case when
> inexplicable magic happens, memory is getting corrupt or overwritten. You
> are obviously prudent about this, but is there no clue when running under
> Valgrind or similar for OSX? Nothing out of the ordinary or warnings?
>
On Tue, Sep 22, 2015 at 6:22 AM, Richard Hipp wrote:
> On 9/22/15, Hugues Bruant wrote:
> >>
> >> If you can capture a malfunctioning trace, and send in the database
> >> file and the SQL statement that is running, that should allow us to
> >> l
Forgot to include the db in the previous email.
On Tue, Sep 22, 2015 at 12:37 AM, Hugues Bruant wrote:
> If you can capture a malfunctioning trace, and send in the database
>> file and the SQL statement that is running, that should allow us to
>> localize the proble
>
> If you can capture a malfunctioning trace, and send in the database
> file and the SQL statement that is running, that should allow us to
> localize the problem.
>
Trace for the failing UPDATE:
cv_s=1
cv_o=b8b9f4...
cv_t=28 -> 29
SQL: [update cv set cv_t=? where cv_s=? and cv_o=?]
VDBE
On Mon, Sep 21, 2015 at 8:43 PM, Richard Hipp wrote:
> On 9/21/15, Hugues Bruant wrote:
> >
> > I would be happy to build and test a patched sqlite with extra logging,
> > some sort of vdbe execution tracing
>
> Compile with -DSQLITE_DEBUG and then use "
On Mon, Sep 21, 2015 at 8:23 PM, Richard Hipp wrote:
> On 9/21/15, Hugues Bruant wrote:
> > On Mon, Sep 21, 2015 at 6:49 PM, Richard Hipp wrote:
> >
> >> On 9/21/15, Hugues Bruant wrote:
> >> > Table schema:
> >> >
> >> > CREA
On Mon, Sep 21, 2015 at 6:49 PM, Richard Hipp wrote:
> On 9/21/15, Hugues Bruant wrote:
> > Table schema:
> >
> > CREATE TABLE cv (cv_s integer not null, cv_o blob not null, cv_t integer
> > not null, primary key(cv_s, cv_o));
> >
> > Prepared statement:
>
> Ideally, open the database which exhibits the problem and first execute
>
> PRAGMA integrity_check;
>
Integrity check does not report any issue.
> If this fails to show any problems run your UPDATE command, repeatedly if
> necessary, and see if you can make the shell tool do anything that
Table schema:
CREATE TABLE cv (cv_s integer not null, cv_o blob not null, cv_t integer
not null, primary key(cv_s, cv_o));
Prepared statement:
UPDATE cv SET cv_t=? where cv_s=? and cv_o=?;
Most of the time the row is updated as expected but in some rare cases
we've seen this statement fail
12 matches
Mail list logo
