From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | Jimmy Thrasibule <thrasibule(dot)jimmy(at)gmail(dot)com> |
Cc: | Chris Travers <chris(dot)travers(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL as a triple store |
Date: | 2014-08-12 15:33:13 |
Message-ID: | 20140812113313.dd6f73a5a98069d7ca856269@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 12 Aug 2014 16:57:32 +0200
Jimmy Thrasibule <thrasibule(dot)jimmy(at)gmail(dot)com> wrote:
> > 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 attribute type
> or even per attribute for the values, I can easily index them for
> quick lookups.
Couple of things to keep in mind:
* SQLLite and PostgreSQL are not 100% compatable. It's cheap and easy to
set up PostgreSQL for testing/development, so it seems silly (to me) to test
on something that might behave differently than the production environment.
* Any setup where the application can execute DDL is a potential security
concern. If the code can manipulate tables then a bug in the code can
allow an accidental or malicious user to quickly and easily destroy data.
--
Bill Moran
I need your help to succeed:
http://gamesbybill.com
From | Date | Subject | |
---|---|---|---|
Next Message | David Carpio | 2014-08-12 16:30:39 | Re: pgcluu |
Previous Message | Raymond O'Donnell | 2014-08-12 15:29:32 | Re: PostgreSQL as a triple store |