> -----Original Message----- > From: Chris Carter [mailto:[EMAIL PROTECTED] > Sent: 04 November 2003 14:17 > To: 'D. Richard Hipp' > Subject: RE: [sqlite] Big Players League > > > [EMAIL PROTECTED] wrote: > > I fear this problem will become even more acute when PHP5 > comes out of > > beta. People will see that SQLite is bundled and wonder "Am > I suppose > > to use SQLite in place of MySQL now?" I think we need a guide > > for helping people to make that choice. We need to help people > > better understand when is it appropriate to use SQLite and > when MySQL > > is a better option. > > > > If any readers would care to attempt to write such > documentation, or > > even just start a Wiki page containing ideas of what such a > document > > should look like, your contributions will be greatly appreciated. > > -- > > D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565 > > Richard, > > I have only just arrived to sqlite and I haven't got a clue > about how it works (internals) but Windows users will > understand the difference between Jet databases (*.mdb) and > SQLServer. Is this the kind of analogy you are looking for > between sqlite and big players? Only that sqlite is miles > better than jet! (I have my own horror stories about jet). > > IMHO, some points to look for are: > - Enterprise or workgroup > - Centralized or standalone > - Built-in or runs externally > > Hope this helps. I guess the 3 items above are pretty much > the same, but just different view angles on the same thing. > > Cheers! > Chris >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
