Thanks for all the suggestions and everyone appears to agree that if
the applications don't need to share data, then I should split them up
into separate database and nothing more.
I appreciate your input and explanations as well.
-Carlos
--
Sent via pgsql-general mailing list (pgsql-general@po
Just trying to understand good DBA design practice. This is obviously
a very general question but any feedback on what good or bad issues
would come from me dumping all my tables for applications in one
database or spread out across multiple databases on PostgreSQL.
Thank you!
As a general rule
On Wed, Feb 02, 2011 at 11:44:51AM -0800, John R Pierce wrote:
> On 02/02/11 11:24 AM, Joshua D. Drake wrote:
>> Forget separate databases. Use separate users with schemas.
>
> for canned applications like mediawiki and phpbb? not sure they
> support that.
>
If they use different users you can
carlos.menn...@gmail.com (Carlos Mennens) writes:
> I was sitting down thinking the other day about when is it good to
> generate a new database or just use an existing one. For example, lets
> say my company name is called 'databasedummy.org' and I have a
> database called 'dbdummy'. Now I need Po
Forget separate databases. Use separate users with schemas.
for canned applications like mediawiki and phpbb? not sure they support
that.
Mediawiki does -- I'm doing just that. It's been liberating learning how
PostgreSQL deals with schemas (and applying that knowledge).
-- Gary Chambers
-
On 02/02/11 11:24 AM, Joshua D. Drake wrote:
Forget separate databases. Use separate users with schemas.
for canned applications like mediawiki and phpbb? not sure they
support that.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
On Wed, 2011-02-02 at 11:08 -0800, John R Pierce wrote:
> On 02/02/11 10:32 AM, Carlos Mennens wrote:
> I would create a seperate database for each thing that has nothing to do
> with the other things.I doubt mediawiki and phpbb will ever share
> any data, they are totally different applicat
ailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Wednesday, February 02, 2011 2:09 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Database Design Question
On 02/02/11 10:32 AM, Carlos Mennens wrote:
> I was sitting down thinking the other day about when is it
On 02/02/11 10:32 AM, Carlos Mennens wrote:
I was sitting down thinking the other day about when is it good to
generate a new database or just use an existing one. For example, lets
say my company name is called 'databasedummy.org' and I have a
database called 'dbdummy'. Now I need PostgreSQL to
I was sitting down thinking the other day about when is it good to
generate a new database or just use an existing one. For example, lets
say my company name is called 'databasedummy.org' and I have a
database called 'dbdummy'. Now I need PostgreSQL to manage several
applications for my company:
-
One solution is to create partial index:
create unique index indice on emails(direccion) where estado = 'A'
_
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
-
Hi all:
Let's say I'm designing a database (Postgres 7.3) with a list of all
email accounts in a certain server:
CREATE TABLE emails (
clienteid INT4,
direccion VARCHAR(512) PRIMARY KEY,
login varchar(128) NOT NULL,
password VARCHAR(128),
dominio VARCHAR(256)
);
The PHBs want to have a log of
12 matches
Mail list logo
