I wonder if you were running SQLite on a linux server which stored your files on a remotely linked drive? Some large hosting companies (mediatemple is a great example) link in your files over NFS or other network filesystems, and those can often be a little buggy with regard to file locking. It's no big deal, until you have two servers trying to edit the sqlite db at the same time. That can cause corruption, but there's not really anything the sqlite db guys can do except say not to run it on network drives with buggy file locking. We wouldn't have that problem on camping's hosting. SQLite is used for everything from ruby webapps to storing the address book and notes on an iPod Touch. It's really wide spread and robust. There are almost certainly more instances of sqlite running in the world at any time than oracle, postgres, mysql, combined! I'd bet the email client I'm using to write this is storing my emails in an sqlite database. :)
— Jenna On Thursday, 26 April 2012 at 7:02 PM, Nokan Emiro wrote: > Hi, > > In a previous thread I was declared as a newbie end user, now I'll behave > like that :) > > If I'll use the hosting service, I'll want to be able to use mysql and not > sqlite, > and other experimental solutions. You can say that this is silly of me, but, > as an end user, I have the right to be silly. BTW I have bad experience > with sqlite. It can happen that the database becomes corrupted somehow, > maybe because of not properly handled concurrent accesses, or a ctrl-c in > a bad moment, I don't know. And mysql is faster too. As a silly end user > I would prefer a separately existing permanency layer. This is not a problem > for active record, so I really don't get it why not to use it. (It would be > enough > to have one database for all the users and let the databasename_tablename > structured tablenames solve the rest. Actually the users don't need to know > where is the data stored and how, just use the ActiceRecord API, but they > need to know that it's fast enough and the data is securely stored.) > > I'm sorry, I know I was not really constructive... > > ...end users are always silly... > > > _______________________________________________ > Camping-list mailing list > Camping-list@rubyforge.org (mailto:Camping-list@rubyforge.org) > http://rubyforge.org/mailman/listinfo/camping-list > >
_______________________________________________ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
