Using SQLite as a multi-user database?

[Fredrik Andersson]

Hehe,

Well, no 1 is not an option and no 2 is a bit difficult. I'm making a 
small in-house application behind the back of the giant IT-department 
(1500 or so people). If I let them know what I'm up to they might begin 
to crack down on my (and my other IT-savvy collegues) other 
applications. We're sort of the grease that keeps the engine turning by 
making small, fast and very specialized applications while the 
IT-department makes 10-100 million dollar applications that takes years 
to finish.

I'll try to find a suitable compromise. It probably won't be pretty but 
I'm sure I can cobble something together :P

Cheers,

Fredrik



Ruslan Zasukhin skrev 2010-11-23 19.04:
> On 11/23/10 4:15 PM, "Andre Garzia"<andre at andregarzia.com>  wrote:
>
>> Fredrik,
> Hi Andre,
>
>
>> Instead of risking problems by having concurrent queries to a single SQLite
>> database, why don't you build a middleware?
>
>>  From your email, I understood that the problem is that you can't install a
>> server such as MySQL because the IT dept will be shouting.
> Hmm
>
>> So why don't you
>> use LiveCode to build a little self contained server which talks to SQLite,
>> then all the clients would talk to this same server, this way, there's no
>> concurrent access since everything passes thru the server.
> Hmmmmmmm  :-)|
>
> Fredrick says:
>
>> Oh, and the reason I have to use SQLite is that I can't run any database
>> servers (the IT department would be.... annoyed to say the least).
> Once again:
>       Fredrick thinks that IT department will not allow
>          ANY db server.
>
> If to make OWN "self contained server which talks to SQLite" and
>      "all the clients would talk to this same server"
>
> ... then sorry?  What difference to "ANY DB Server" ?
>
>
> Fredrik,
>
> The only ways for you are:
>
> 1) forget about multi-user access
>
> 2) take coffee with your IT guys and explain them that you NEED
>      a multi-user DB server.
>
>
>