> I think you're going to need to perform experiments and decide if the
flexibility you get is worth the performance you're going to lose.
> As you can see from John R Pierce's response it is only matter of time
before someone (correctly) warns you about the performance issues with EAV
derivatives,
> Is there a reason why hstore or json is not an option? That may work a lot
> better than this approach.
I don't want to move away from SQL common features so I can have a
test environment using SQLite and deploy on PostgreSQL. This approach
looks elegant and simple to me. Using a new table per
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
tryi
