| From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
|---|---|
| To: | "Richard_D_Levine(at)raytheon(dot)com" <Richard_D_Levine(at)raytheon(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 'Official' definition of ACID compliance? |
| Date: | 2006-01-05 20:11:49 |
| Message-ID: | c2d9e70e0601051211h2a6b4d4csfe243ae13b3737c2@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/5/06, Richard_D_Levine(at)raytheon(dot)com <Richard_D_Levine(at)raytheon(dot)com> wrote:
>
>
> pgsql-general-owner(at)postgresql(dot)org wrote on 01/05/2006 01:59:52 PM:
> <snip>
> > so the problem is that MySQL _forces_ a consistent state but in the
> > process it violates the integrity of the data
> >
> That is a contradiction in terms. Data integrity is a requirement of
> database consistency.
>
>
maybe, but it seems what happen in MySQL... because it forces a
consistent state (one the fullfill the rules and constraints of the
database) but when doing it it breaks or silently change your data...
so the data can be saved because it's legal data but not correct
data... then it is consistent to the machine but not for you...
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph M. Day | 2006-01-05 20:15:32 | Suse Linux 10.0 |
| Previous Message | Ketema Harris | 2006-01-05 19:51:46 | Best Data type for Binary Data? |