Search Postgresql Archives

Re: multi-company design/structure ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 20 October 2009 10:11:53 am Wolfgang Keller wrote:
> > Is it better to create multi databases or create multi schemas?
>
> You're missing one option imho: One database, one schema.
>
> > I am writing a program that can have multi instances.  Sort like a
> > finanical accounting system that can have multiable companies. Where each
> > company has a different name but the tables are an exact match to each
> > other.
>
> Then you could simply add a "company-id" column to every table (and make
> this column part of the primary key of each table). And if you run multiple
> instances of the program within _one_ company, then you can also add an
> "instance-id" column (and make this column also part of the primary key of
> each table).
>
> Sincerely,
>
> Wolfgang

I never even considered using the one database with added company 
field/column.  On the surface is sounds OK but I'm not to sure.  Each SQL 
statement would require company_id.  Hmmmm.

Johnf



-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux