pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Raymond O'Donnell <rod@iol.ie>
To: Archana K N <archanakknn@gmail.com>
To: itb348@gmail.com, guillaume@lelarge.info, PostgreSQLPHP PostgreSQLPHP <pgsql-php@postgresql.org>
Subject: Re: How to Create a table in another database
Date: Fri, 13 Nov 2015 11:54:41 +0000
Message-ID: <5645CF81.9020601@iol.ie> (raw)
In-Reply-To: <CACa6=i2cKRUXH9xcG00PREhu=bwG1tcr7-q-q3OsJN6=G2hyJQ@mail.gmail.com>
References: <CACa6=i0J0WPTvikpeO0=VdoAiux1+MCwx4dc1=OZmO_b7GG23w@mail.gmail.com>
	<CAECtzeVAOHF2pBd8dZg+Q4FEzDYT1fdP1_ssozPB6S_LqbvLMw@mail.gmail.com>
	<5644F4DB.9010702@googlemail.com>
	<CACa6=i2cKRUXH9xcG00PREhu=bwG1tcr7-q-q3OsJN6=G2hyJQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-php>

On 13/11/2015 05:35, Archana K N wrote:

>  Here the underlined queries are for /db2.  /I need to create function
> in the second database since first database contain data that is not for
> public access. So from second database I call the *db1.retriev *and it
> uses necessary data from *db1 *and result is saved as a table in second
> database. Actual function has more parameters and result may contain
> many rows , for that I want to create table in */db2/*.

Have you considered using two separate schemas within the same database?
You can set permissions on them so that one is for public access and the
other isn't; it would be far easier than messing with two databases.

Ray.


-- 
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie


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



view thread (7+ messages)  latest in thread

Message-ID: <5645CF81.9020601@iol.ie>
Permalink:  ../5645CF81.9020601@iol.ie/
Also on:    postgresql.org/message-id/5645CF81.9020601@iol.ie

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: rod@iol.ie, archanakknn@gmail.com
  Subject: Re: How to Create a table in another database
  In-Reply-To: <5645CF81.9020601@iol.ie>
  References: <CACa6=i0J0WPTvikpeO0=VdoAiux1+MCwx4dc1=OZmO_b7GG23w@mail.gmail.com> <CAECtzeVAOHF2pBd8dZg+Q4FEzDYT1fdP1_ssozPB6S_LqbvLMw@mail.gmail.com> <5644F4DB.9010702@googlemail.com> <CACa6=i2cKRUXH9xcG00PREhu=bwG1tcr7-q-q3OsJN6=G2hyJQ@mail.gmail.com> <5645CF81.9020601@iol.ie>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox