On Tue, Apr 29, 2014 at 8:16 PM, Kay C Lan wrote:
> I've just done a check and I'm not seeing any error. I use to get something
> like 'table not available' or 'table doesn't exist'. All I'd have to do was
> close the management tool and LC would work properly again. So a couple of
> years ago I
On Mon, Apr 28, 2014 at 10:59 PM, Peter Haworth wrote:
> I'm also interested in what type of errors you've encountered that make
> your database inaccessible? SQLite is most definitely designed for multiple
> connections,
>
> Well this appears to be the 2nd change that's happened to LC + SQLite
r
Well I guess it depends on the application but how do you manage locks
and/or cursors when continually opening/closing?
I'm also interested in what type of errors you've encountered that make
your database inaccessible? SQLite is most definitely designed for multiple
connections, just not by diffe
orn coders, some achieve coding, and some have coding thrust upon
them." - William Shakespeare & Hugh Senior
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Really-basic-SQLite-questions-tp4678662p4678776.html
Sent from the Revolution - User mailing list ar
On Sat, Apr 26, 2014 at 12:04 AM, Mike Kerner wrote:
> Bob, I agree that in general... Since SQLite is a local file-store DB,
> it's a little different. it isn't designed for transaction loads,
> multi-users, etc.
>
Which is why I'll offer one instance where it may make sense to open/close
the
Thanks everyone.
As I am only accessing a local file(s) and there is only a single user at any
one time I will go with connecting at startup and disconnecting at quit.
Externals I will load on the appropriate connection.
Of course if this doesn't work I will report back, but so far everything se
Bob, I agree that in general, when dealing with a server, you are exactly
right on what you should be doing. Since SQLite is a local file-store DB,
it's a little different. it isn't designed for transaction loads,
multi-users, etc. it doesn't even support all the datatypes - for
instance, yes, y
My experience with SQL is that there is a timeout if a connection has been idle
for a certain period of time. Perhaps this is not a problem with sqLite, but as
a matter of good development habits, get all the info you need from the user
BEFORE opening the connection, so that there is no chance o
Hi James,
I'd leave them open until you quit the app. You might also think about
using the ATTACH command for the second and subsequent connections so
they'll all be open on the same connection. This allows you to, for
example, define JOINs across databases, although you'll need to change the
refer
1's easy, so I'll answer that:
sqlite is a text file that is formatted so that it can be treated like a
regular db. So open when you start and close when you're done. I have had
numerous cases on mobile where the app does not get to close the db before
it crashes for whatever reason with no ill e
1. Open and close database connections. When?
Obviously you need to open a connection to access a database, but when do you
need to close it?
Does it close without you doing anything?
I have the need to connect to four db's while running my app.
Access to a couple of these is sporadic but constant
11 matches
Mail list logo
