On 4/13/15 6:21 AM, Anil Menon wrote:
In addition to all these comments
- If you use multiple databases, if you want to keep some "common"
tables (example counties_Table, My_company_details), its going to be a pain
- if you want to access tables across databases - you might need to
start using F
In addition to all these comments
- If you use multiple databases, if you want to keep some "common" tables
(example counties_Table, My_company_details), its going to be a pain
- if you want to access tables across databases - you might need to start
using FDWs (which is going to be a administrati
2015-04-13 10:43 GMT+02:00 Albe Laurenz :
> Michael Cheung wrote:
> > I have many similar database to store data for every customer.
> > Structure of database is almost the same.
> > As I use same application to control all these data, so I can only use
> > one database user to connect to these da
Michael Cheung wrote:
> I have many similar database to store data for every customer.
> Structure of database is almost the same.
> As I use same application to control all these data, so I can only use
> one database user to connect to these database.
> And I have no needs to query table for diff
On 4/13/2015 12:07 AM, Alban Hertroys wrote:
That's easier to backup, sure, but you can't restore a single customer's schema
easily that way. So if one customer messes up their data big time, you'll need
to restore a backup for all customers in the DB.
if you use pg_dump -Fc, then you can spe
> On 13 Apr 2015, at 4:20, Ian Barwick wrote:
>
> On 13/04/15 11:08, Michael Cheung wrote:
>> hi, all;
>>
>> I am new here. And I need some suggestion.
>>
>> I have many similar database to store data for every customer.
>> Structure of database is almost the same.
>> As I use same application
Thanks for your additional comment.
It is more clear, I'd better to using schema more than using database.
yours, michael
On Sun, 12 Apr 2015 19:24:30 -0700
John R Pierce wrote:
> On 4/12/2015 7:20 PM, Ian Barwick wrote:
> > If as you say access to the database is via a single application dat
Thanks for your suggestion.
I'd like to use schema as you suggest.
yours, michael
On Mon, 13 Apr 2015 11:20:59 +0900
Ian Barwick wrote:
> On 13/04/15 11:08, Michael Cheung wrote:
> > hi, all;
> >
> > I am new here. And I need some suggestion.
> >
> > I have many similar database to store data
On 4/12/2015 7:20 PM, Ian Barwick wrote:
If as you say access to the database is via a single application database
user, it will probably make more sense to use multiple schemas rather than
multiple databases. Keeping everything in one database will simplify
administration (e.g. making backups -
On 13/04/15 11:08, Michael Cheung wrote:
> hi, all;
>
> I am new here. And I need some suggestion.
>
> I have many similar database to store data for every customer.
> Structure of database is almost the same.
> As I use same application to control all these data, so I can only use
> one database
hi, all;
I am new here. And I need some suggestion.
I have many similar database to store data for every customer.
Structure of database is almost the same.
As I use same application to control all these data, so I can only use
one database user to connect to these database.
And I have no needs t
11 matches
Mail list logo
