Has this thread got anything at all to do with PHP?
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
>On Mon, 9 Apr 2001, Bob Hall wrote:
>
> > > MySQL is providing an SQL frontend to a
> > >bunch of tables and indices, that is it ... it is up to the programmer to
> > >handle the "managing of data" part where it revolves around being
> > >relational ...
> >
> > I've developed database apps
>
> I'm rooting for PostgreSQL to become the open source app that ate
> Oracle. MySQL will never be capable of that, but I don't think it
> needs to be. There will always be a niche for small, quirky apps that
> have just enough functionality to get the job done and keep the
> learning curve
Doug,
There's something wrong here. This is the internet, we're
disagreeing, but we're not flaming each other. If we keep this up,
they'll revoke all our software licenses because of our noncompliant
behavior.
>Hi Bob!
>
>That would make a very interesting study. Attempting to come up with a
Od: "Bob Hall" <[EMAIL PROTECTED]>
Temat: Re: [PHP-DB] Re: PostgreSQL versus MySQL
> > > The implication is that MySQL is not an RDBMS. The only attempt I
> > > know of to define an RDBMS was Codd's, and no DBMS has ever met the
> > > criter
On Mon, 9 Apr 2001, Bob Hall wrote:
> > MySQL is providing an SQL frontend to a
> >bunch of tables and indices, that is it ... it is up to the programmer to
> >handle the "managing of data" part where it revolves around being
> >relational ...
>
> I've developed database apps in which the data w
>On Sun, 8 Apr 2001, Bob Hall wrote:
>
> > Doug,
> >
> > You've posted your usual good sense, combined with one statement I
> > strongly disagree with.
> >
> > >One of
> > >these products is a relational database management system. The other is a
> > >quasi-SQL-like-front-end-to-systems-o
Hi Bob!
That would make a very interesting study. Attempting to come up with a
modern definition of RDBMS. Of course, it would be only an academic
exercise...but it would be a fascinating paper if any youngsters reading
this from a university dorm room or computer lab would like to tackle it.
On Sun, 8 Apr 2001, Bob Hall wrote:
> Doug,
>
> You've posted your usual good sense, combined with one statement I
> strongly disagree with.
>
> >One of
> >these products is a relational database management system. The other is a
> >quasi-SQL-like-front-end-to-systems-of-indexed-files that has n
Doug,
You've posted your usual good sense, combined with one statement I
strongly disagree with.
>One of
>these products is a relational database management system. The other is a
>quasi-SQL-like-front-end-to-systems-of-indexed-files that has never
>concerned itself with things like standards
Transactions are not for critical data such as credit card numbers. There
are at least a couple of reasons for transactions and neither of the
reasons I can think of are for storing critical data such as credit card
numbers.
Transactions are for updates to the database that must happen all toget
> As for a full comparison between the two, I think the bottom line is
> that MySQL is slightly more light-weight, but easier to use and faster
> than PostgreSQL. So if you're looking for a database for a relatively
> noncritical web application, I'd say go with MySQL, especially since
> that's wh
On the contrary, MySQL is much better at handling table crashes and data corruption
than PostgreSQL is. What you may have heard is that due to lack of transaction
support, critical data may be lost "in transit" from your application to the database,
in the event of a system crash or a dropped c
13 matches
Mail list logo