NYCPHP Meetup

[Joe Crawford]

Adam,

thanks for this clarification.

so if i was going to develop a 3rd party script i should use sqlite
since i cannot gurantee the end user will have access to mysql, although
all hosts i have seen offer mysql, i guess sqlite is only good when you
dont do much writing to the database and only reading, in that case i
will stick with mysql for most of my projects ;)

Joe Crawford Jr.


On Sat, 2004-07-24 at 19:29, Adam Maccabee Trachtenberg wrote:
> On Sat, 24 Jul 2004, Joe Crawford wrote:
> 
> > i was asking if anyone has used sqlite and if it was better than using
> > mysql etc...
> 
> Okay. In that case my answer is SQLite is better than MySQL in some
> instances and worse in others. :)
> 
> In many ways this is a somewhat vague question because you haven't
> qualified your question with the type of application you're trying to
> develop.
> 
> SQLite is better:
>   * When your application requires a database and you can't depend on
> one being installed.
>   * When you have mostly read only data.
>   * When you want triggers.
>   * When you want typeless fields.
>   * When you want to write custom UDFs in PHP.
>   * When you don't want to worry about the GPL.
> 
> MySQL is better:
>   * When you have lots of reads mixed in with writes.
>   * When you need access control, such as what's done using the GRANT command.
>   * When you need replication.
>   * When you want to communicate using SSL.
>   * When you want typed fields.
>   * When want to chose a GPL product.
>   * When you want paid support.
> 
> SQLite and MySQL both have subselects and transactions.
> 
> -adam


>From hans not junk at nyphp.com  Sat Jul 24 19:36:38 2004
Return-Path: <hans not junk at nyphp.com>
Received: from smtp11.intermedia.net (smtp11.intermedia.net [64.78.21.10])
	by virtu.nyphp.org (Postfix) with ESMTP id ED739A8633
	for <talk at lists.nyphp.org>; Sat, 24 Jul 2004 19:36:37 -0400 (EDT)
Received: from ehost011-1.exch011.intermedia.net ([64.78.21.3]) by
	smtp11.intermedia.net with Microsoft SMTPSVC(6.0.3790.0); 
	Sat, 24 Jul 2004 16:36:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [nycphp-talk] XAMPP: Upgrading MySQL
Date: Sat, 24 Jul 2004 16:36:35 -0700
Message-ID: <41EE526EC2D3C74286415780D3BA9F870334B2DB at ehost011-1.exch011.intermedia.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [nycphp-talk] XAMPP: Upgrading MySQL
Thread-Index: AcRxzmgm/Qjgec5hR9+CUOLsJgMT1AABvJQA
From: "Hans Zaunere" <hans not junk at nyphp.com>
To: "NYPHP Talk" <talk at lists.nyphp.org>
X-OriginalArrivalTime: 24 Jul 2004 23:36:37.0501 (UTC)
	FILETIME=[101622D0:01C471D7]
X-BeenThere: talk at lists.nyphp.org
X-Mailman-Version: 2.1.4
Precedence: list
Reply-To: NYPHP Talk <talk at lists.nyphp.org>
List-Id: NYPHP Talk <talk.lists.nyphp.org>
List-Unsubscribe: <http://lists.nyphp.org/mailman/listinfo/talk>,
	<mailto:talk-request at lists.nyphp.org?subject=unsubscribe>
List-Archive: <http://lists.nyphp.org/pipermail/talk>
List-Post: <mailto:talk at lists.nyphp.org>
List-Help: <mailto:talk-request at lists.nyphp.org?subject=help>
List-Subscribe: <http://lists.nyphp.org/mailman/listinfo/talk>,
	<mailto:talk-request at lists.nyphp.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jul 2004 23:36:38 -0000


> anyone here know how hard/easy it is to upgrade the mysql version that
> is pre-packed with XAMPP?

Not sure... certainly doable, I'd imagine, but you'd probably be getting
into the realm of installing a separate MySQL instance on the box and
disabling that which comes with XAMPP.

> they have version 4.0.20 and i would like to upgrade to 4.1

Be careful here... there's a major difference between the two.  Chances
are, your code will break.

MySQL 4.1.x uses a new binary protocol, and requires the
http://php.net/mysqli extension to work.  You can set MySQL to be
backwards compatible, but then you'll miss the benefits of the binary
protocol (prepared statements, no escaping, etc).

> also anyone here used the SQLite extension?  Is this better to use
than
> MySQL?

It really depends what you need.  In a word (and disclaimer: I work for
MySQL :)  SQLite isn't a RDBMS.  It's strictly a local file-system based
SQL system; it's truly a SQL enabled file system.  MySQL allows users to
connect remotely, has much more functionality, and is much faster as
load scales up.  If your application has any significant load,
especially that of write-queries, you should go with MySQL.  MySQL is
also very common on hosting platforms (more so than SQLite).

H