search

ericsink / SQLitePCL.raw

A Portable Class Library (PCL) for low-level (raw) access to SQLite
Apache License 2.0
512 stars 106 forks source link

sqlite3_file_control access #556

Open dk307 opened 9 months ago

dk307 commented 9 months ago

SQLitePCLRaw handles many platforms and configurations. If you are having trouble, we typically need a LOT of information from you in order to help figure out what is going wrong.

The following questions are provided to help you see what kinds of information we need:

What version of SQLitePCLRaw are you using? 2.1.6

If you are using one of the SQLitePCLRaw bundle packages, which one? SQLitePCLRaw.batteries_v2.dll SQLitePCLRaw.core.dll SQLitePCLRaw.provider.dynamic_cdecl.dll SQLitePCLRaw.provider.sqlite3.dll SQLitePCLRaw.ugly.dll

What platform are you running on? What operating system? Which version? What CPU? Win 11, x64

What target framework are you building for? .net framework 4.6.2

Are you on .NET Framework or the newer stuff (.NET Core, .NET 5+, etc)? .net framework 4.6.2

Are you using the command line, or an IDE? Which IDE? Which version of that IDE? VS 2022

Is this problem something that just started happening? For example, were things working well for you and then you updated something and then the problem showed up? What changed? I am unable to set file_control via sqlite3_file_control. It seems it is not exposed in ugly or raw classes.

What is the exact error message you are seeing when the problem happens?

Are you using PackageReference or packages.config?

If you are using mobile platforms, are you on classic/legacy Xamarin or on .NET 6 and higher?

Sometimes other packages using SQLitePCLRaw cause problems when they are mixed together. What other packages are you including in your project?

How can we reproduce the problem you are seeing? Your issue will get attention much faster if you attach a minimal reproduction sample project.

ericsink commented 8 months ago

I acknowledge this as a feature request to support the sqlite3_file_control API. I'll follow-up with more info after I look to see what that would entail.