Re: problem with table structure - Mailing list pgsql-general

From Tim Landscheidt
Subject Re: problem with table structure
Date
Msg-id m3sk3sddq3.fsf@passepartout.tim-landscheidt.de
Whole thread Raw
In response to problem with table structure  (Miguel Vaz <pagongski@gmail.com>)
Responses Re: problem with table structure  (Miguel Vaz <pagongski@gmail.com>)
List pgsql-general
Miguel Vaz <pagongski@gmail.com> wrote:

> I was looking for an opinion on the actual table structure. :-) How should i
> build the data set? Is my second example ok? The first is the long version
> but i wanted to put together all the common fields to both types of "sites"
> and then (maybe) build tables to accomodate the specific fields so there are
> no empty columns on the table if i put everything in the same table.
> [...]

That's way too fuzzy for good advice. Few people build data
sets on archaeological sites, and even those probably don't
use all the same structure.

Tim
(not telepathic)

pgsql-general by date:

Previous
From: Leif Jensen
Date:
Subject: Open Source references
Next
From: "tamanna madaan"
Date:
Subject: "attempted to lock invisible tuple" error while update