From: | "Morgan Kita" <mkita(at)verseon(dot)com> |
---|---|
To: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Advice on custom data types |
Date: | 2005-03-22 01:49:16 |
Message-ID: | 08B420FF5BF7BC42A064212C2EB768801C1090@neutron.verseon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
In my initial database schema I have certain relational tables that could strongly be thought of as objects. As an example one table might hold a bunch of related points(x,y,z) where the rows could be grouped by a foreign key to another table. Anotherwords each set of points belongs to one row in another table.
So from what I have been reading here in the forums its usually best to avoid custom data types, but I would not be querying on the fields contained in the possible objects, nor would I be indexing on them. It would essentially just be storing them and extracting them as needed. Would this be a good case for a custom data type, written as a C struct?
From | Date | Subject | |
---|---|---|---|
Next Message | Derrick Betts | 2005-03-22 03:24:21 | Select Interval in plpgsql |
Previous Message | John DeSoi | 2005-03-22 00:31:07 | Re: .pgpass file |