Along these lines.
Did you guys see the link to the new full managed C# version of SqlLite?
http://code.google.com/p/csharp-sqlite/
Holey schmoley! As much as I like managed code, I must ask why on earth
would they bother? I have the source code for SQLite and it's goddamn
enormous and has
I think these lines from the FAQ might give us cause to worry. I think I'll
stick to the SQLite ADO.NET provider until I hear otherwise - Greg
Q: Since SQLite has a dll and exe you can download why port to C#?
A: It was an exercise to learn the C# language
Q: Should I report bugs to
Along these lines.
Did you guys see the link to the new full managed C# version of SqlLite?
http://code.google.com/p/csharp-sqlite/
On 11 January 2012 16:12, Greg Keogh g...@mira.net wrote:
Now it’s coming back a bit. I remember a bulk load was running for over 4
hours and I wondered what the
Folks, I've been using SQLite for many months now and as I previously said,
it plays nicely with EF4. However I just found out by accident that SQLite
does not enforce foreign key constraints. I didn't realise until I performed
a bulk load of my database with thousands of incorrect PK and FK
Greg, Greg, Greg... /sigh Didn't you discover this six or so months ago?
I seem to recall someone saying you had to put a pragma in the query
or some such. I still don't use SQLite so I don't really know. But I
do remember you bringing this up some time ago.
David
If we can hit that
or some such. I still don't use SQLite so I don't really know. But I
do remember you bringing this up some time ago.
I must be losing my marbles. Two nights ago I went through it for what
seemed the first time. Groundhog day?! -- Greg
I actually think that what you brought up 6 months ago was about doing a
SQLite bulk insert and it being particularly slow until you discovered you
needed to use a PRAGMA statement to speed it up.
So, while you may be losing your marbles, it's probably independent of this
foreign key issue :)
On
David,
I think that was in addition rather than instead of, but I'm not going
to bother checking. Of course, I've written code for the first time
only to discover it already done with my name on it :/
Me: No, those scripts don't exist.
Colleague: Here they are, and they have your name on them.
Now it's coming back a bit. I remember a bulk load was running for over 4
hours and I wondered what the hell was wrong. It turns out you have to wrap
the inserts in an explicit transaction, otherwise it seems to create a
silent transaction for each insert and it's slow beyond belief. The clue to
