| From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL not ACID compliant? |
| Date: | 2003-09-20 00:27:04 |
| Message-ID: | 20030919212633.E6867@ganymede.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 19 Sep 2003, Joshua D. Drake wrote:
> Hello,
>
> Sorry guys I made the unbelievable mistake of talking on the #mysql
> channel today. Can you believe that they
> actually feel that the fact that you can insert data outside the
> boundaries of the data type (int for example) and
> mySQL won't throw an exception is still valid ACID compliance.
>
> There argument is that the application (user) should not have tried to
> insert bad data. I was completely blown
> away. The C in ACID explictly states that internal (data type boundaries
> anyone) AND user defined constraints
> can not be violated.
>
> I am just flabbergasted. I am going to come back to my safe PostgreSQL
> world.
Boy, I'm flabbergasted that you actually believed them ... tsk tsk ...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2003-09-20 00:48:26 | Re: PostgreSQL not ACID compliant? |
| Previous Message | Joshua D. Drake | 2003-09-20 00:17:06 | Re: PostgreSQL not ACID compliant? |