Re: [sqlite] VFS xFullPathname cannot access URI parameters

On 2/26/20, Chris Warner wrote: > In 3.31.1, attempting to access URI Parameters via the sqlite3_uri_* > functions inside a VFS xFullPathname function returns junk. This was not an > issue in 3.30.1 or 3.31.0. > SQLite does not promise that sqlite3_uri_parameter() will work for the argument

Re: [sqlite] VFS implementation for SoC

Thank you. It appears that the POSIX function fsync of the SoC has some problem syncing to the local spiffs, but the whole thing works for an external SD filesystem. Regards Arun On Fri, 12 Apr 2019 18:58:36 +0530 Richard Hipp wrote > On 4/12/19, Arun - Siara Logics (cc) wrote:

Re: [sqlite] VFS implementation for SoC

On 4/12/19, Arun - Siara Logics (cc) wrote: > Hi, > > Please ignore the earlier emails. The extended error code when trying > CREATE TABLE is 1034 and when trying INSERT is 266. You can now visit https://www.sqlite.org/rescode.html and search for "1034" and "266" to find out what those errors

Re: [sqlite] VFS implementation for SoC

Hi, Please ignore the earlier emails. The extended error code when trying CREATE TABLE is 1034 and when trying INSERT is 266. I have given below the correct log generated during INSERT. Thanks. Regards Arun Enter file name: /spiffs/test.db fn: FullPathNamefn:Fullpathname:Success fn: Open

Re: [sqlite] VFS implementation for SoC

I also tried INSERT on an existing database. This time the extended error is 266. I am giving below the log. Also, there are two warnings printed during open: (21) API call with invalid database connection pointer (21) misuse at line 152855 of [fb90e7189a] Regards Arun Enter file name:

Re: [sqlite] VFS implementation for SoC

Hi, Thank you for the suggestion. The sqlite3_extended_errcode() is 1034 disk I/O error. Regards Arun On Fri, 12 Apr 2019 17:06:00 +0530 Richard Hipp wrote > On 4/12/19, Arun - Siara Logics (cc) wrote: > > fn:DirectWrite:Success > > fn:FlushBuffer:Success > > fn:Sync:Success

Re: [sqlite] VFS implementation for SoC

On 4/12/19, Arun - Siara Logics (cc) wrote: > fn:DirectWrite:Success > fn:FlushBuffer:Success > fn:Sync:Success > SQL error: disk I/O error > > At the end, there are two files on disk: vfs_test.db (0 bytes) and > vfs_test.db-journal (512 bytes). There is no problem reading a database. > But when

Re: [sqlite] VFS FCNTL question

Hello, On 2017-12-03 17:41, J Decker wrote: https://sqlite.org/c3ref/c_fcntl_busyhandler.html #define SQLITE_FCNTL_PDB 30 SQLITE_FCNTL_PDB has no documentation as to what it's for. The only place, where this FCNTL is used, is btree.c:sqlite3BtreeOpen(). The FCNTL informs a VFS driver on

Re: [sqlite] vfs question: how to pass binary/blob arg to xCreate()?

You could try Unicode binary encoding to increase the efficiency when passing binary as strings: https://qntm.org/unicodings > On Oct 20, 2017, at 7:20 PM, Liam Staskawicz wrote: > > Hi, > > I'm just getting started exploring the vfs capabilities

Re: [sqlite] vfs question: how to pass binary/blob arg to xCreate()?

On 10/20/17, Liam Staskawicz wrote: > Hi, > > I'm just getting started exploring the vfs capabilities of sqlite, and > am interested in providing a binary blob argument to xCreate(), No. The arguments to xCreate() are copies of the arguments to the CREATE VIRTUAL TABLE

Re: [sqlite] vfs?

ot;General Discussion of SQLite Database" <sqlite-users@sqlite.org> Sent: Sunday, June 17, 2012 8:46 PM Subject: Re: [sqlite] vfs? Thanks for your prompt respnse. Well, no, really. I don't know where my application will be used. Maybe someone will use it under linux or OS2, all I know i

Re: [sqlite] vfs?

Subject: Re: [sqlite] vfs? Arbol One <arbol...@programmer.net> wrote: > Using C/C++, is there a way to extract which file system is SQLite using? You already know that - it's the one you've specified in a call to sqlite3_open_v2. What problem are you trying to solve? -- Igor

Re: [sqlite] vfs?

Arbol One wrote: > Using C/C++, is there a way to extract which file system is SQLite using? You already know that - it's the one you've specified in a call to sqlite3_open_v2. What problem are you trying to solve? -- Igor Tandetnik

Re: [sqlite] VFS minor issue with xDelete method return value

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31/10/11 09:25, Всеволод Новиков wrote: > I am using sqlite 3.7.8. > > My custom VFS xDelete method returned SQLITE_NOTFOUND in a case when > the file to be deleted was not found, and this worked fine for older > versions (probably prior to 3.7.x

Re: [sqlite] VFS

It appears that Qt (or more accurately, WebKit) had defined SQLITE_OMIT_LOAD_EXTENSION and a couple of other symbols at compile time, and therefore when Qt opens a database, it uses a slightly different VFS than the default VFS contained in sqlite3.c (i.e., no xDl* members are set). I believe now

Re: [sqlite] VFS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 02:39 PM, Robert Hairgrove wrote: > On Tue, 2011-02-22 at 08:46 -0800, Roger Binns wrote: >> What you think you are seeing is not happening. The documentation is >> correct. > > OK ... but what about that which the GDB debugger is

Re: [sqlite] VFS

On Tue, 2011-02-22 at 08:46 -0800, Roger Binns wrote: > On 02/22/2011 05:29 AM, Robert Hairgrove wrote: > > I'm trying to understand how the VFS implementation works. > > What you think you are seeing is not happening. The documentation is correct. OK ... but what about that which the GDB

Re: [sqlite] VFS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 05:29 AM, Robert Hairgrove wrote: > I'm trying to understand how the VFS implementation works. What you think you are seeing is not happening. The documentation is correct. > However, if I open a database and inspect the VFS

Re: [sqlite] VFS Layer for to split databaseinto several files?

On Mon, Jul 19, 2010 at 12:47:18PM -0700, James Croall scratched on the wall: > Hi Michael, > > I agree -- while in theory it shouldn't be difficult, the testing and > verification would be painful! And it's unclear to me from glancing through > the code how locking should be handled -- probably

Re: [sqlite] VFS Layer for to split database into several files?

What "modern" system doesn't support NFSV3? They might have that turned on by default for their file export to legacy systems perhaps. The two systems should default to the highest version supported by both so who's holding the show? Are you running your application on another Linux box?

Re: [sqlite] VFS Layer for to split databaseinto several files?

Of Black, Michael (IS) > Sent: Monday, July 19, 2010 12:42 PM > To: j...@kreibi.ch; General Discussion of SQLite Database; General > Discussion of SQLite Database > Subject: Re: [sqlite] VFS Layer for to split databaseinto several > files? > > Oops -- my bad...I guess I never ran

Re: [sqlite] VFS Layer for to split databaseinto several files?

Oops -- my bad...I guess I never ran into that problem in the "old" days. I know I used to write 2Gig+ files on 32-bit Linux before it was popular. So...perhaps the next logical question is...can this guy's user put NFSV3 or such on? Would be a lot easier than writing your own split-VFS

Re: [sqlite] VFS Layer for to split database into several files?

S) > Sent: Monday, July 19, 2010 10:51 AM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] VFS Layer for to split database into several > files? > > Also...would you care to elucidate what environment you're in that > limits you to 2GB? > > I've heard nume

Re: [sqlite] VFS Layer for to split database into several files?

Also...would you care to elucidate what environment you're in that limits you to 2GB? I've heard numerous people before who think they're limited when, in actuality, they're not. Michael D. Black Senior Scientist Advanced Analytics Directorate Northrop Grumman Information Systems

Re: [sqlite] VFS Layer for to split database into several files?

> I'm stuck with an environment with a 2GB file size limit. What the exact problem do you see and how do you compile SQLite? All modern compilers have macros _LARGEFILE_SOURCE or _FILE_OFFSET_BITS=64 defined by default and with that SQLite works perfectly with any files with more than 2GB in

Re: [sqlite] VFS implementation guidance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brown, Daniel wrote: > Is it possible to change the VFS SQLite is using while SQLite is > running? You can call sqlite3_vfs_register/unregister at any point. Note that SQLite does no inuse tracking so it will happily let you unregister a VFS

Re: [sqlite] VFS implementation guidance

king to switch VFS during program start-up and > before any databases are loaded or used. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Roger Binns > Sent: Tuesday, November 04, 2008 12:39 PM > To: General Discussion of SQLi

Re: [sqlite] VFS implementation guidance

during program start-up and before any databases are loaded or used. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Binns Sent: Tuesday, November 04, 2008 12:39 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] VFS implementation

Re: [sqlite] VFS implementation guidance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brown, Daniel wrote: > Are there any guides to implementing a VFS (sqlite3_vfs) for SQLite? A > good practices guide would be as useful. I already have an existing > file system API/library for the target system so I guess it is mostly > just

Re: [sqlite] vfs implementation question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeffrey Becker wrote: > Cool. I'm actually working on extending Robert Simson's ADO.Net > provider to allow vfs implementations to be written in managed code. I'm doing the same in my Python wrapper for SQLite (APSW). One feature I have implemented

Re: [sqlite] vfs implementation question

Cool. I'm actually working on extending Robert Simson's ADO.Net provider to allow vfs implementations to be written in managed code. I hope to get at least two custom vfs implementations into his codebase, a custom memory backed vfs and a true client-server vfs. On Tue, Aug 19, 2008 at 5:45 PM,

Re: [sqlite] vfs implementation question

D. Richard Hipp wrote: > On Aug 19, 2008, at 9:02 AM, Jeffrey Becker wrote: > > >> Should the xLock member of sqlite3_io_methods object block until the >> lock can be acquired? > > xLock does not block on any of the built-in VFSes. But if you want to > make your own custom VFS that blocks on

Re: [sqlite] vfs implementation question

On Aug 19, 2008, at 9:37 AM, Jeffrey Becker wrote: > So in the cases where the lock cant be acquired, the built in vfs > implementations return SQLITE_BUSY? > Yes D. Richard Hipp [EMAIL PROTECTED] ___ sqlite-users mailing list

Re: [sqlite] vfs implementation question

So in the cases where the lock cant be acquired, the built in vfs implementations return SQLITE_BUSY? On Tue, Aug 19, 2008 at 9:16 AM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > > On Aug 19, 2008, at 9:02 AM, Jeffrey Becker wrote: > >> Should the xLock member of sqlite3_io_methods object block

Re: [sqlite] vfs implementation question

On Aug 19, 2008, at 9:02 AM, Jeffrey Becker wrote: > Should the xLock member of sqlite3_io_methods object block until the > lock can be acquired? xLock does not block on any of the built-in VFSes. But if you want to make your own custom VFS that blocks on locks, I don't know of any reason

Re: [sqlite] VFS memory leak : During lock / unlock operations

* Dennis Cote: > The OP said they were measuring an excess of lock calls. That would > imply that SQLite is locking files it has already locked. Is that > possible with the POSIX APIs? SQLite uses fcntl-based locks, which keep a separate lock for each byte in a file (or, more precisely, any

Re: [sqlite] VFS memory leak : During lock / unlock operations

Dennis Cote <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > > There are no lock leaks. But on the other hand, there is not > > a one-to-one mapping of lock to unlock calls. unlock is called > > more often than lock and there are often attempts to unlock files > > that have never

Re: [sqlite] VFS memory leak : During lock / unlock operations

[EMAIL PROTECTED] wrote: > > There are no lock leaks. But on the other hand, there is not > a one-to-one mapping of lock to unlock calls. unlock is called > more often than lock and there are often attempts to unlock files > that have never been locked, irrc. This is harmless on windows > and

Re: [sqlite] VFS memory leak : During lock / unlock operations

<[EMAIL PROTECTED]> wrote: > Hi.. > >we are using sqlite3.3.4 with Integrity OS. we are facing a problem > where in the VFS memory is getting exhausted due >to large lock/unlock calls made by sqlite. Integrity support team > said that, for each file lock call made by sqlite, a definite

Re: [sqlite] VFS memory leak : During lock / unlock operations

Brad House <[EMAIL PROTECTED]> wrote: > >> they have put traces and identified that for 1000 lock calls > >> there are only 950 unlock calls, which is a shortage of 50 unlock > >> calls. > > The os_unix.c backend to SQLite makes no attempt to match lock/unlock > > calls, because posix does not

Re: [sqlite] VFS memory leak : During lock / unlock operations

>> they have put traces and identified that for 1000 lock calls >> there are only 950 unlock calls, which is a shortage of 50 unlock >> calls. > The os_unix.c backend to SQLite makes no attempt to match lock/unlock > calls, because posix does not requires such. If you are running > on an

Re: [sqlite] VFS memory leak : During lock / unlock operations

: [sqlite] VFS memory leak : During lock / unlock operations <[EMAIL PROTECTED]> wrote: > Hi.. > >we are using sqlite3.3.4 with Integrity OS. we are facing a problem > where in the VFS memory is getting exhausted due >to large lock/unlock calls made by sqlite. I

Re: [sqlite] VFS memory leak : During lock / unlock operations

From: Murthy Girigowda (WT01 - TES-Access Networks) Sent: Friday, February 08, 2008 12:25 PM To: 'sqlite-users@sqlite.org' Subject: VFS memory leak : During lock / unlock operations Hi.. we are using sqlite3.3.4 with Integrity OS. we are facing a

RE: [sqlite] VFS in upcoming 3.5.0

You can create a 'shared memory VFS' to share a memory database against other thread / processes, and you can also 'copy' the RAW bytes of your memory with memcpy from/to another storage to accomplish the serialize / load you want to wire transfer SQLite memory databases. But this is not a simple

Re: [sqlite] VFS in upcoming 3.5.0

>> 1. As known, an InMemory-DB is currently not (much) faster >>than working against a File. >>With the new VFS I think, that much faster InMemory- >>DB-Handling should be possible, is that right? > I don't think so. The vfs is really an interface for moving > data (pages) in and

Re: [sqlite] VFS in upcoming 3.5.0

On Sat, 2007-09-01 at 08:15 -0700, Olaf Schmidt wrote: > Hi, > > first - congrats to the planned changes in the new, upcoming > version of SQLite. The new shared-cache behaviour sounds > promising and also the new VFS-option. > > A few questions to VFS. > 1. As known, an InMemory-DB is