]
Sent: Wednesday, March 03, 2004 1:28 PM
To: [EMAIL PROTECTED]; Mark Warner; [EMAIL PROTECTED]
Subject: Re: PgSQL vs MySQL
As a DBA and someone who has worked both with PostgresQL and MySQL, I think
I can answer this knowingly.
First, MySQL is significantly faster than PostgresQL and Oracle
What advantages, besides ease of setup, does MySQL hold over PostgreSQL?
It would seem, to me, that the two are close competitors (both in
quality, and performance).
Are you sure about quality? Check out:
http://sql-info.de/mysql/gotchas.html
You can check out postgresql's on the same
David wrote:
Are you sure about quality? Check out:
http://sql-info.de/mysql/gotchas.html
Those have nothing to do with the quality of MySQL.
I don't think i'd trust it for anything critical
unless you very confident your developers know what they are doing.
Would you trust anything to
Are you sure about quality? Check out:
http://sql-info.de/mysql/gotchas.html
Those have nothing to do with the quality of MySQL.
No? Why not?
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL MS SQL
Server.
Upscene Productions
Would you trust anything to developers who do not know what they are doing?
As a _novice_ developer I learned the noted aspects of MySQL: it's part of knowing
how the database works and how to use it, and not terribly sophisticated.
Then you may be a good developer but experience tells me
The thing which bothers me most about MySQL is the lack of a proper
boolean. I don't like having to abstract a tinyint(1) into true or
false. As much of my work involves building applications with Yes or No
questions, I think I am switching to PostgreSQL.
[EMAIL PROTECTED] wrote:
What
In the last episode (Mar 03), [EMAIL PROTECTED] said:
Would you trust anything to developers who do not know what they
are doing?
As a _novice_ developer I learned the noted aspects of MySQL: it's
part of knowing how the database works and how to use it, and not
terribly
:-)
someflag enum('TRUE','FALSE');
Not quite boolean, but it works.
Curtis
On Wed, 3 Mar 2004, Mark Warner wrote:
The thing which bothers me most about MySQL is the lack of a proper
boolean. I don't like having to abstract a tinyint(1) into true or
false. As much of my work involves
Message -
From: [EMAIL PROTECTED]
To: Mark Warner [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 6:51 AM
Subject: Re: PgSQL vs MySQL
What advantages, besides ease of setup, does MySQL hold over PostgreSQL?
It would seem, to me, that the two are close competitors (both
from the manual it appears that char(0) null default null can be
used as a boolean, will the values of either null or . haven't
tried it myself, but its documented.
http://www.mysql.com/documentation/mysql/bychapter/manual_Column_types.html#Column_types
[NATIONAL] CHAR(M) [BINARY | ASCII |
.
Davi.
- Original Message -
From: David Griffiths [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; Mark Warner
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 10:27 AM
Subject: Re: PgSQL vs MySQL
As a DBA and someone who has worked both with PostgresQL and MySQL, I
think
I
InnoDB that you like, and not MySQL
specifically?
-James
-Original Message-
From: David Griffiths [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 10:28 AM
To: [EMAIL PROTECTED]; Mark Warner; [EMAIL PROTECTED]
Subject: Re: PgSQL vs MySQL
As a DBA and someone who has worked both
I do not approve or disapprove of your choice of Postgres over MySQL.
I don't profess to be a postgresql expert, i'm still learning about it.. but a quick
glance at the documentation tells me that the only option would be to use pg_dump
utility which creates a sql file. I haven't looked at
]; [EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 10:27 AM
Subject: Re: PgSQL vs MySQL
As a DBA and someone who has worked both with PostgresQL and MySQL, I
think
I can answer this knowingly.
First, MySQL is significantly faster than PostgresQL and Oracle.
Second, MySQL is also a simpler
is MyQL. MySQL offeres multiple persistence engines - InnoDB, MyISAM
(ISAM), heap, and BDB. It is shipped by default with MySQL.
David
- Original Message -
From: James Kelty [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 10:51 AM
Subject: RE: PgSQL vs MySQL
Curtis Maurand wrote:
:-)
someflag enum('TRUE','FALSE');
Not quite boolean, but it works.
Curtis
On Wed, 3 Mar 2004, Mark Warner wrote:
The thing which bothers me most about MySQL is the lack of a proper
boolean. I don't like having to abstract a tinyint(1) into true or
false. As much of
Michael,
I couldn't agree more! I didn't even realize there was a boolean issue
until now. I don't really understand the issue of using 0 as false, and
1 as true. The way I view it is that true and false are merely
abstract names for 0 and 1. When the database is accessed using Java, I
don't
On Wed, Mar 03, 2004 at 10:51:40AM -0800, James Kelty wrote:
As a DBA I have a few questions about what you said here.
You have worked with both PostgreSQL and MySQL, and yet you say that
MySQL is 'signifigantly' faster than Oracle? Can you PROVE that?
For a given set of data and workload,
, March 03, 2004 1:28 PM
To: [EMAIL PROTECTED]; Mark Warner; [EMAIL PROTECTED]
Subject: Re: PgSQL vs MySQL
As a DBA and someone who has worked both with PostgresQL and MySQL, I think
I can answer this knowingly.
First, MySQL is significantly faster than PostgresQL and Oracle.
Second, MySQL is also
I know, I get it, I was trying for humor.
Curtis
On Wed, 3 Mar 2004, Michael Stassen wrote:
Curtis Maurand wrote:
:-)
someflag enum('TRUE','FALSE');
Not quite boolean, but it works.
Curtis
On Wed, 3 Mar 2004, Mark Warner wrote:
The thing which bothers me most
20 matches
Mail list logo
