- June 25, 2015
- 584
- 292
- Home Country
- United Kingdom
- Thread starter
- #61
I'm not using SQLiteClient - I'm using Entity Framework and LINQ. However, I have converted some SQLiteClient code because we still need some old code in MP - because of dynamic queries. They now connect - do stuff - disconnect; and there is no performance issue. As a user you simply wouldn't notice.I have to disagree with that (or perhaps I'm misunderstanding you, do you indeed do a new SQLiteClient for each query?)
I'm using postgres at work quite extensively and if I create a new postgres connection for every query I want to do that certainly takes it's time. (don't ever see something like an internal database cache for that...)
But, even when I used SQL, back in 1994, with stored procedures or in-line SQL, I did a project where I was tasked with testing the difference between Oracle connects first time and subsequently. The first connect always took a while and all connects after that were quick. I'm talking about connect - do stuff - disconnect - every time. Once you've done the first connect all connects thereafter are pretty much negligible, performance wise.
The same is true for SQLBase, SQL Server and now, in my experience, SQLite.
You're not the first person I have heard saying that .