[GENERAL] strategies for segregating client data when using PostgreSQL in a web app

2012-08-03 Thread Menelaos PerdikeasSemantix
I would like to know what are the best practices / common patterns (or pointers to such) for using PostgreSQL in the context of a big web application with substantial data per user. Namely, we are designing an ERP / accounting / business intelligence Web Application where each client company will

Re: [GENERAL] strategies for segregating client data when using PostgreSQL in a web app

2012-08-03 Thread Chris Angelico
On Sat, Aug 4, 2012 at 6:05 AM, Menelaos PerdikeasSemantix mperdikeas.seman...@gmail.com wrote: [1] use just one database and schema and logically segregate companies data by having all tables have a client_id column as part of their primary key. [2] use multiple database (in the same server

Re: [GENERAL] strategies for segregating client data when using PostgreSQL in a web app

2012-08-03 Thread Rory Campbell-Lange
On 03/08/12, Menelaos PerdikeasSemantix (mperdikeas.seman...@gmail.com) wrote: I would like to know what are the best practices / common patterns (or pointers to such) for using PostgreSQL in the context of a big web application with substantial data per user. ... [1] use just one database and

Re: [GENERAL] strategies for segregating client data when using PostgreSQL in a web app

2012-08-03 Thread David Johnston
From: pgsql-general-owner@postgresql .org [mailto:pgsql-general-owner@postgresql .org] On Behalf Of Menelaos PerdikeasSemantix Sent: Friday, August 03, 2012 4:05 PM To: pgsql-general@postgresql .org Subject: [GENERAL] strategies for segregating client data when using PostgreSQL in a web app I