Re: [sqlite] kooky thought: a vm-only build (for embedded).feasible?

... > > size -- both code and RAM. I know about the various > compile switches that > > can turn off various features, but I wonder if I can really > strip it down > > further by eliminating parsing, query planning, etc, > altogether, and only > > support the virtual machine. I do need

Re: [sqlite] kooky thought: a vm-only build (for embedded). feasible?

On 4/15/18, dave wrote: > I had a stray thought, and wanted to ask if it's been thunk before,and if so > what is the thinking? Or just for commentary. > > I have been building a system, part of which uses sqlite and virtual tables. > This is working great in a desktop/mobile

Re: [sqlite] kooky thought: a vm-only build (for embedded).feasible?

to approach the surgery. -dave > -Original Message- > From: sqlite-users > [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On > Behalf Of Simon Slavin > Sent: Sunday, April 15, 2018 2:06 PM > To: SQLite mailing list > Subject: Re: [sqlite] kooky tho

Re: [sqlite] kooky thought: a vm-only build (for embedded). feasible?

On 15 Apr 2018, at 7:54pm, dave wrote: > I wonder if I can really strip it down > further by eliminating parsing, query planning, etc, altogether, and only > support the virtual machine. I wonder what you would find if you looked through the data structure of

[sqlite] kooky thought: a vm-only build (for embedded). feasible?

I had a stray thought, and wanted to ask if it's been thunk before,and if so what is the thinking? Or just for commentary. I have been building a system, part of which uses sqlite and virtual tables. This is working great in a desktop/mobile environment. However, eventually one day, I will