Accommodating alternative column values

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Accommodating alternative column values
Date: 2024-07-02 21:47:12
Message-ID: fd94aff-aec9-1b3d-64c6-16b0eaeccc58@appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In data made available from a state regulatory agency I find a few instances
where a facility contact has two email addresses. While multiple locations
are accommodated because they're in a table separate from the facility name
and details, all people associated with a facility and location are in a
'people' table with only one column for an email addresse.

While I could enter an additional email address in the 'comment' column if
I'm entering data for a single facility, I'm reformatting the downloaded
data so I can insert all new table data from one .sql file. Is there a way
to accommodate multiple email addresses other than entering both with a
forward slash separating them in the varchar(64) email address column?

Suggestions appreciated,

Rich

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2024-07-02 21:50:27 Re: Accommodating alternative column values
Previous Message clipperDB 2024-07-02 16:13:04 printing PGresult content with gdb