Skip site navigation (1) Skip section navigation (2)

Re: Need concrete "Why Postgres not MySQL" bullet list

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Ian Barwick" <barwick(at)gmx(dot)net>,"Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Need concrete "Why Postgres not MySQL" bullet list
Date: 2003-08-21 01:42:45
Message-ID: 00d201c36785$8661bf10$2800a8c0@mars (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-generalpgsql-hackers
> Oh dear, this excludes my usual one-item "things to think about
> when considering what database to use":
> 
> * PROPER USAGE OF NULL
> 
> mysql> select * from ai_test where id is null;
> +----+-------+
> | id | txt   |
> +----+-------+
> |  1 | hello |
> +----+-------+
> 1 row in set (0.00 sec)
> 
> ;-). I digress. Off the top of my head, in no particular order:

You're not trying hard enough:

mysql> create table test3 (a date);
Query OK, 0 rows affected (0.00 sec)

mysql> insert into test3 values (-1);
Query OK, 1 row affected (0.01 sec)

mysql> insert into test3 values ('1996-02-31');
Query OK, 1 row affected (0.00 sec)

mysql> insert into test3 values ('1996-67-31');
Query OK, 1 row affected (0.00 sec)

mysql> select * from test3;
+------------+
| a          |
+------------+
| 0000-00-00 |
| 1996-02-31 |
| 0000-00-00 |
+------------+
3 rows in set (0.00 sec)

I find that even funnier...

Chris


In response to

pgsql-hackers by date

Next:From: Jan WieckDate: 2003-08-21 02:10:10
Subject: Re: Buglist
Previous:From: Alvaro HerreraDate: 2003-08-21 01:29:08
Subject: Re: Buglist

pgsql-advocacy by date

Next:From: Shridhar DaithankarDate: 2003-08-21 09:15:03
Subject: Re: Need concrete "Why Postgres not MySQL" bullet list
Previous:From: Anastasios HatzisDate: 2003-08-20 22:44:42
Subject: Re: Need concrete "Why Postgres not MySQL" bullet

pgsql-general by date

Next:From: jasonDate: 2003-08-21 01:48:34
Subject: Your details
Previous:From: Alvaro HerreraDate: 2003-08-21 01:29:08
Subject: Re: Buglist

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group