| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Curt Sampson" <cjs(at)cynic(dot)net>, "Hannu Krosing" <hannu(at)tm(dot)ee> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why is MySQL more chosen over PostgreSQL? |
| Date: | 2002-07-31 02:43:30 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOIEGNCDAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I highly doubt that. Relating two tables to each other via a key, and
> joining them together, allows you to do everything that inheritance
> allows you to do, but also more. If you have difficulty with keys and
> joins, well, you really probably want to stop and fix that problem
> before you do more work on a relational database....
I'm still not convinced of this. For example, my friend has a hardware
e-store and every different class of hardware has different properties. ie
modems have baud and network cards have speed and video cards have ram. He
simply just has a 'products' table from which he extends
'networkcard_products', etc. with the additional fields. Easy.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-07-31 02:44:26 | Re: Why is MySQL more chosen over PostgreSQL? |
| Previous Message | Bruce Momjian | 2002-07-31 02:43:07 | Re: getpid() function |