| From: | <kaiq(at)realtyideas(dot)com> |
|---|---|
| To: | sheila bel <sheilabel(at)hotmail(dot)com> |
| Cc: | pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: [GENERAL] using ID as a key |
| Date: | 2000-02-04 17:58:13 |
| Message-ID: | Pine.LNX.4.10.10002041156020.24310-100000@picasso.realtyideas.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
search for oid and serial or sequence, referential or foreign key
in the doc or archive of this list. there are a lot lot very good
advices.
On Fri, 4 Feb 2000, sheila bel wrote:
> Hi,
>
> I'm new to data base design so please bare with me if my
> question is so basic..
> I'm designing a database, two of the tables are EMPLOYEES and
> AGENCIES. I need an ID for each of them. I would also need to
> have the agencyID in the EMPLOYEES table so that I can identify
> which agency they belong to something like a foreign key. I know
> postgreSQL does not support it so how do I implement this ?
> What kind of data type should I use for the ID ? In general I
> do not know how to implement IDs and use them as keys.
> I've read the user manual and a bit of the programmer's
> manual several times but haven't found anything that will
> apply to this situation.
>
> Please Help. Thank You.
>
> -Sheila
>
>
>
>
> ************
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marten Feldtmann | 2000-02-04 18:15:31 | Re: [SQL] Re: [HACKERS] Proposed Changes to PostgreSQL |
| Previous Message | Marc Tardif | 2000-02-04 17:43:59 | Re: [GENERAL] using ID as a key |