From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Chris Travers <chris(at)travelamericas(dot)com> |
Cc: | CSN <cool_screen_name90001(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 8.1 vs. MySQL 5.0? |
Date: | 2005-10-13 16:11:02 |
Message-ID: | 1129219862.29961.189.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general |
On Thu, 2005-10-13 at 00:32, Chris Travers wrote:
> Scott Marlowe wrote:
> >Strict Mode and Error handling: Not an option, but always on in
> >PostgreSQL. There are still plenty of things that "fall through the
> >cracks" on MySQL, like my previously mentioned problem with column level
> >constraints (specificall fk but all column level constraints are
> >ignored, no error, no warning, no notice.) Jeez, how hard would it be
> >to just throw a danged notice?
> >
> >
> Or worse, do you want an RDBMS where an application can turn of data
> verification and then insert dates like Feb 31, 2005? (Strict mode can
> be enabled/disabled per connection/session)
> <snip>
Oh my dear god, you have got be kidding! No way to lock out bad data
then? ugh.
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Turner | 2005-10-13 17:00:03 | Re: PostgreSQL 8.1 vs. MySQL 5.0? |
Previous Message | Andreas Pflug | 2005-10-13 08:52:58 | Re: [GENERAL] Oracle buys Innobase |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2005-10-13 16:20:53 | On "multi-master" (was: Limitations of PostgreSQL) |
Previous Message | Aly S.P Dharshi | 2005-10-13 16:06:51 | Re: Cluster/redundancy question |