Re: PostgreSQL as a triple store - Mailing list pgsql-general
| From | Seref Arikan |
|---|---|
| Subject | Re: PostgreSQL as a triple store |
| Date | |
| Msg-id | CA+4Thdp-BLc5Acw-RfByX1zVR6UVA+s2PUNxJwsKBA8YJXnbcg@mail.gmail.com Whole thread Raw |
| In response to | PostgreSQL as a triple store (Jimmy Thrasibule <thrasibule.jimmy@gmail.com>) |
| Responses |
Re: PostgreSQL as a triple store
(Chris Travers <chris.travers@gmail.com>)
Re: PostgreSQL as a triple store (Jimmy Thrasibule <jimmy.thrasibule@gmail.com>) |
| List | pgsql-general |
I've developed solutions where I've used EAV along with a more relational design, they were delivered on time, performed at the expected/acceptable level, so no problems. Then again, I've tried to use EAV bluntly in a healthcare related project and it died on me quite quickly when the data grew.
Seref
Hello,
I'm looking into gathering information about geographical locations:
- Coordinates
- Place name
- Pictures
- etc.Since a place can be anything, a specific place may need any kind of data type to be described.
I'm therefore looking into using the same method as the semantic Web and trying to describe a place with triples.
1. The "triples" table will reference a subject, attribute and value.
2. The "attributes" table will have an attribute name, a type and mauve a table name.
3. For each attribute type, a new table is created to store the values.
4. A "resources" table list all the available resources (location, picture, ...).Using this, I can easily add a new resource and describe it by adding new triples. Every item is identified using UUIDs as primary key.
This seems too simple to be true so I falling back to you in case you see any pitfalls here.
The "triples" table will grow very fast in this setup and may become a bottleneck. However, I don't see any other way to store information about something as wide as places around the world.
Regards,
Jimmy
pgsql-general by date: