Alrighty, thank you for the compatibility know-how between the two and for such
a great product overall.
V/r,
Ryan
-Original Message-
From: sqlite-users-bounces at mailinglists.sqlite.org
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Richard Hipp
Sent: Tuesday, May
--> But it does work with System.Data.SQLite.
Would that entail a mandatory reconstruction of the System.Data.SQLite project
to utilize SEE for compatibility on the C++ side as well?
Adding to both would be a good idea as Mike N suggested, but for clarity to
the superiors, I would like
I seem to be getting a foreign key check anomaly. I've checked the constraint
mentioned in the error message (and the other one, just in case). Am I
overlooking something, or has this been fixed since 3.8.4.1?
sqlite> pragma foreign_key_check;
Error: foreign key mismatch - "Field"
I am a big fan of SQLite and the elegance and simplicity of it and fossil. The
documentation and support are excellent.
Given that the team takes a long-term perspective, I would prefer if the s/w
was structured in a more modular fashion so that various components were usable
as libraries e.g.
System.Data.SQLite I believe has its own SEE implementation embedded. Unsure
if its compatible with SEE or not. In order to access an encrypted DB outside
of System.Data.SQLite, the same encryption module would have to be available in
your C++ implementation.
If your project has this
On 5/17/16, Ryan Irwin wrote:
>
> --> But it does work with System.Data.SQLite.
> Would that entail a mandatory reconstruction of the System.Data.SQLite
> project to utilize SEE for compatibility on the C++ side as well?
Yes, as it stands now, you have to recompile SDS using MSVC. And that
is a
Hello together!
I am struggling with a memory issue of SQLite and therefore searching for help.
The database of our product has about 70GB of data. When I call the "PRAGMA
integrity_check" method, the memory consumption of my system continuously
increases until all of my 16GB of RAM are used.
On 5/16/16, Ryan Irwin wrote:
>
> I am aware of the SEE but am lead to believe that it may be proprietary and
> would not match the encryption method used by the DotNet and
> SQLite.Interop.
>
SEE is indeed proprietary. (http://www.hwaci.com/sw/sqlite/see.html).
But it does work with
On Tue, 17 May 2016 11:09:53 +1000
"dandl" wrote:
> Any disagreement so far?
Full agreement; your description is perfectly sound.
I am quite certain nevertheless that LIMIT has no relational basis.
Nothing based on Order By could. And I'll try to clear up what I meant
by a cursor.
> So
On Tue, 17 May 2016 11:09:53 +1000
"dandl" wrote:
> > I'll invent here and now to replace LIMIT: nth().
>
> The issue is find the "top N". This does not solve the problem.
nth() does find "top N". For any query, nth(c, N) returns N rows. It
also exposes the arbitrariness of LIMIT. To use
> > > > first second
> > > > - --
> > > > MarkSpark
> > > > Emily Spark
> > > > MarySoper
> > > > Brian Soper
> > > >
> > > > SELECT first,second FROM members ORDER BY second LIMIT 3
>
> First, hat tip to Simon for providing a motivating example. :-)
>
> The question
Please take this to another thread!
> On 16 May 2016, at 23:16, Objective C wrote:
>
> Thank you for your answer,
> here is the code i used to backup my SQLite database :
>
> var source = new SQLiteConnection("Data Source = MyDB.db ; Version = 3;");
> var destination = new
On Mon, 16 May 2016 19:14:01 +, Objective C
wrote:
> Hi sir,
> In fact, i have an issue with SQLite database Restore using c#
That's not what this discussion thread is about, it would have
been better if you sterted a new thread, but anyway.
> i'm coding a button which can restore an
Hi ,
yes, this is perfectly understood. but my quesion is around the CEROD
extension. the sqlite driver does not support DBs which are created with CEROD
based compression.
thanks
Tal
> On May 16, 2016, at 10:53 PM, Klaas Van B. wrote:
>
> Did you read, understood and used all instructions you
14 matches
Mail list logo
