| From: | Gábor Farkas <gabor(at)nekomancer(dot)net> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | Jim Nasby <jnasby(at)pervasive(dot)com>, Jimbo1 <jamestheboarder(at)googlemail(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Advantages of PostgreSQL over MySQL 5.0 |
| Date: | 2006-03-24 08:51:29 |
| Message-ID: | 4423B311.2060907@nekomancer.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Scott Marlowe wrote:
> On Thu, 2006-03-23 at 12:17, Jim Nasby wrote:
>> On Mar 22, 2006, at 10:08 PM, Scott Marlowe wrote:
>>> Now, I shouldn't be able to insert anything in b that's not
>>> referencing
>>> an entry in a. and I used innodb tables. and I used ansi SQL, and I
>>> got no errors. So how come my data's incoherent three seconds after
>>> creating the tables the way the spec says should work? Simple. MySQL
>>> only implements foreign keys if you do them this way:
>
> Yep. I filed the bug report on it.
>
> http://bugs.mysql.com/bug.php?id=13301
>
from the response:
> Years ago, to help porting applications from other database brands to
> MySQL, MySQL was made to accept the syntax even though no real
> constraints were created.
i hope postgresql will never "help" me this way.
gabor
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2006-03-24 08:58:55 | Re: COPY command documentation |
| Previous Message | Devrim GUNDUZ | 2006-03-24 07:57:19 | Re: where to find pg_config.... |