| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | CSN <cool_screen_name90001(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL 8.1 vs. MySQL 5.0? |
| Date: | 2005-10-06 19:56:36 |
| Message-ID: | 1128628595.29347.239.camel@state.g2switchworks.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general |
On Thu, 2005-10-06 at 14:35, CSN wrote:
> --- Scott Marlowe <smarlowe(at)g2switchworks(dot)com> wrote:
>
> >
> > But what really bugs me is that some things that ARE
> > bugs simply aren't
> > getting fixed and probably won't. Specifically,
> > while mysql understands
> > fk references made at a table level, it simply
> > ignores, without error,
> > warning, or notice, fk references made in a column.
> > arg... Very
> > frustrating. If they just didn't support that
> > syntax it would be much
> > less bothersome, since I'd try it, get an error, and
> > try the other
> > syntax. Instead, I spent an afternoon trying to
> > figure out why it
> > wasn't doing ANYTHING when I declared an FK
> > reference at column level.
> >
> > Things like that are, sadly, kinda rampant in MySQL.
> >
>
> What's the difference between a fk at the table level
> vs. column level? The only fk's I've used are one
> column referencing another.
It's just where they're defined. See this bug for an explanation:
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-10-06 20:12:17 | Re: [GENERAL] PostgreSQL 8.1 vs. MySQL 5.0? |
| Previous Message | Alex Turner | 2005-10-06 19:42:44 | Re: PostgreSQL 8.1 vs. MySQL 5.0? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-10-06 20:12:17 | Re: [GENERAL] PostgreSQL 8.1 vs. MySQL 5.0? |
| Previous Message | CSN | 2005-10-06 19:54:43 | Re: PostgreSQL Gotchas |