sqlite-net: Issue: 'SQL logic error' when upgrading to version 1.7.335 (UWP)

I’m having a SQL script that is giving me an error when I upgrade to version 1.7.335 of the sqlite-net-pcl version. Version 1.6.292 it is working fine.

Actual

Exception SQL logic error is thrown.

Expected

No issues

Reproduction

I’ve created a repository with a reproduction scenario: https://github.com/rneeft/SqliteNetIssue. To see the issue (and a working version):

Start debugging
Click the button
Verify that everything is working (Debugger stops at line 91)
Stop debugging
Upgrade sqlite-net-pcl to the latest version 1.7.335
Start debugging
Click the button
Exception SQL logic error is thrown.

The files 0039 and 0044 are similar (except for the content) and I don’t see anything that could cause this issue. Executing the files in SQL Server works fine.

Any help is very appreciated.

About this issue

Original URL
State: open
Created 4 years ago
Comments: 17 (5 by maintainers)

Most upvoted comments

https://github.com/ericsink/SQLitePCL.raw/wiki/UWP-Init

ericsink on Sep 1, 2020

So I guess I could just leave out calling it again?

Probably.

With “always specify a path” you mean when providing the database location when creating a SQLiteConnection?

First of all, remember that the sentence in which I said “always specify a path” expressed a lot of uncertainty, because you basically asked for my conjecture about cases where things worked even though sqlite3_win32_set_directory was not called.

Strictly speaking, what I mean is to specify a full path when calling sqlite3_open() or sqlite3_open_v2(). In most cases, a wrapper library (such as sqlite-net) is calling that for you. Yes, creating a SQLiteConnection sounds right, but I don’t really know. I’ve never used sqlite-net myself and I am not familiar with its API. I only maintain the layer underneath it.

ericsink on Mar 22, 2022