From: | merlyn(at)stonehenge(dot)com (Randal L(dot) Schwartz) |
---|---|
To: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Humor me: Postgresql vs. MySql (esp. licensing) |
Date: | 2003-10-08 16:20:55 |
Message-ID: | 86r81n7law.fsf@blue.stonehenge.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>>>>> "Shridhar" == Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> writes:
Shridhar> Yeah.. like inserting a biiig number in integer field in a transaction
Shridhar> without error and not getting it back after commit.. or accepting
Shridhar> '00-00-00 00:00:00' as a valid datetime stamp.. something like that..
Shridhar> How much deviation is that from ACID? 180 degrees...:-)
Unverified, but you can apparently try to store a huge number into a
short integer, and MySQL silently truncates to maxint. No error. No
warning.
No place for it in a real business environment. :(
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn(at)stonehenge(dot)com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-10-08 16:25:57 | Re: Possible bug on insert |
Previous Message | scott.marlowe | 2003-10-08 16:14:04 | Re: Humor me: Postgresql vs. MySql (esp. licensing) |