Hellom,
I am using the c# variant of sqlite (system.sqlite.data.org) and am using a
connection string similar to this:
public static string OMconnectionString = "datasource=database.db; Default
Timeout=20; PRAGMA busy_timeout = 600; PRAGMA synchronous=Off";
I then use the following statements to
Thank you. Exactly so. One of the problems with this kind of project is
finding 'good enough' challenges to tackle.
I'll let you know how I get on.
[BTW I don't remember the last time I saw SQL like this. Understanding it
might be the challenge...]
Regards
David M Bennett FACS
Andl - A New
On 9 Jun 2015, at 6:52pm, giles burgess wrote:
> Looking at the query plan
Did you run ANALYZE after creating your tables, views and indexes ?
Simon.
On 06/09/2015 04:46 PM, Samuel Debionne wrote:
> Hello,
>
> AFAIU, when executing a drop statement on a virtual table, the XConnect
> callback is executed first, then XDestroy.
>
> Now I have the following scenario where my virtual table is related to a
> file (say a CSV file):
>
> 1. Create the
On Sun, 7 Jun 2015 21:36:51 +0200
George wrote:
> On Sat, 06 Jun 2015 21:14:46 +0700
> Dan Kennedy wrote:
>
> > On 06/06/2015 03:19 AM, George wrote:
> > > Hello everyone,
> > >
> > > I am new to the list. I am working on an application in which I
> > > will be embedding SQLite as the database
I think you'd be in a minority. I went through the first 50 questions about
SQLite on Stack Overflow and only one was C++. Android/Java are dominant,
with a smattering of C# and various other languages. Those are my target
users, eventually.
C/C++ is the drug of choice for low-level byte and bit
You need to see code to know if you're interested. But I take your point:
the grammar is here: http://www.andl.org/downloads/.
Regards
David M Bennett FACS
Andl - A New Database Language - andl.org
-Original Message-
From: sqlite-users-boun...@mailinglists.sqlite.org
Mike McWhinney wrote:
>
> public static string OMconnectionString = "datasource=database.db;
> Default Timeout=20; PRAGMA busy_timeout = 600; PRAGMA synchronous=Off";
>
The connection string should contain name/value pairs, delimited by "="
and ";" (i.e. connection string properties), not SQL
Removing the persistant instance of a virtual table is the most common way of
tripping up a virtual table implementation.
Just because xCreate and xConnect have identical interfaces does not mean that
they are identical (although, with care, you can use the same routine to
perform both tasks).
At 13:50 09/06/2015, you wrote:
>BTW I don't remember the last time I saw SQL like this. Understanding it
>might be the challenge
`---
Most probably! I can imagine that you don't encounter such style in
common business-like environments.
Take your time, this SQL piece is clearly beyond
On Tue, Jun 9, 2015 at 1:50 PM, wrote:
> Thank you. Exactly so. One of the problems with this kind of project is
> finding 'good enough' challenges to tackle.
>
See also from the CTE doc:
- https://www.sqlite.org/lang_with.html#sudoku
- https://www.sqlite.org/lang_with.html#mandelbrot
Thanks,
On Tue, 9 Jun 2015 15:13:47 +
Hick Gunter wrote:
> xConnect is called whenever SQLite decides it needs to do something
> with the existing virtual table. There must have been a successful
> xCreate call (in another session, another thread or another process)
> before. xConnect is not allowed
I think without your actual schema and query plan it might be hard to tell,
but generally the optimizer is not a panacea, it's limited in what it can
divine from your queries.
On Tue, Jun 9, 2015 at 10:52 AM, giles burgess wrote:
> Hi, I have a question about the SQLite query optimizer.
>
> I
Hello,
AFAIU, when executing a drop statement on a virtual table, the XConnect
callback is executed first, then XDestroy.
Now I have the following scenario where my virtual table is related to a
file (say a CSV file):
1. Create the virtual table
2. Delete the CSV file from disk
3. Try to drop
Hi, I have a question about the SQLite query optimizer.
I have a SQLite embedded database with a star-like schema, with the wrinkle
that each record in the fact table can map to a range of records in each
dimension table. This is represented in the fact table as min and max
rowids for each
At 08:27 09/06/2015, you wrote:
>Andl is at a slightly higher level than SQL for writing simple queries.
>Where it shines is writing complex queries that involve user-defined
>types,
>custom transformations and custom aggregations. For complex relational
>operations there is nothing I know
I hope you do try it. I'm looking for feedback.
Sorry about the C#. Problem is, I'm way more productive in C# than any other
language. C/C++ is just too slow to get things done and Java is still lagging.
It would have taken far longer to do the SQLite C interface without .NET
interop (JNI is
17 matches
Mail list logo
