From: | Zak McGregor <zak(at)mighty(dot)co(dot)za> |
---|---|
To: | "Martin A(dot) Marques" <martin(at)math(dot)unl(dot)edu(dot)ar>, pgsql-general(at)postgresql(dot)org |
Cc: | Steve Leibel <stevel(at)bluetuna(dot)com> |
Subject: | Re: MySQL has transactions |
Date: | 2001-01-24 14:34:36 |
Message-ID: | 200101241434.QAA01398@zak.home.dom |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Wed, 24 Jan 2001 10:18:56 -0300
"Martin A. Marques" <martin(at)math(dot)unl(dot)edu(dot)ar> wrote:
> El Mié 24 Ene 2001 08:06, Zak McGregor escribió:
> >
> > Other irritations I've found with MySQL are (briefly):
> > - no subselects (makes for ugly hacks in code)
> > - no views
> > - no foreign keys
>
> Didn't know they didn't have foreign keys. :-(
Not only that - this is what the MySQL site used to say about foreign
keys:
The FOREIGN KEY syntax in MySQL exists only for compatibility with other
SQL vendors CREATE TABLE commands: It doesn't do anything.
...
Foreign keys is something that makes life very complicated, because the
foreign key definition must be stored in some database and
then the hole [sic] 'nice approach' by using only files that can be moved,
copied and removed will be destroyed. In the near future we will extend
FOREIGN KEYS so that the at least the information will be saved and may be
retrieved by mysqldump and ODBC.
Ciao
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2001-01-24 14:37:49 | VACUUM ANALYZE FAILS on 7.0.3 |
Previous Message | Bruce Momjian | 2001-01-24 14:27:12 | Re: Multiple columns w/single aggregate |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-01-24 14:34:37 | Re: [BUGS] select cash_out('2'); crashes backend on 7.0.2 |
Previous Message | Bruce Momjian | 2001-01-24 14:24:48 | Re: WAL fsync scheduling |