Scott Marlowe wrote:
> On Sun, Aug 24, 2008 at 10:19 PM, Troy Rasiah <[EMAIL PROTECTED]> wrote:
>>
>> Scott Marlowe wrote:
>>> On Sun, Aug 24, 2008 at 8:43 PM, Troy Rasiah <[EMAIL PROTECTED]> wrote:
Sorry for bringing up an old post...If you have a generic set of tables..
eg. table
On Sun, Aug 24, 2008 at 10:19 PM, Troy Rasiah <[EMAIL PROTECTED]> wrote:
>
>
> Scott Marlowe wrote:
>> On Sun, Aug 24, 2008 at 8:43 PM, Troy Rasiah <[EMAIL PROTECTED]> wrote:
>>> Sorry for bringing up an old post...If you have a generic set of tables..
>>>
>>> eg. table of countries / post codes et
Scott Marlowe wrote:
> On Sun, Aug 24, 2008 at 8:43 PM, Troy Rasiah <[EMAIL PROTECTED]> wrote:
>> Sorry for bringing up an old post...If you have a generic set of tables..
>>
>> eg. table of countries / post codes etc which are used across several
>> databases what is the best way to access / sto
On Sun, Aug 24, 2008 at 8:43 PM, Troy Rasiah <[EMAIL PROTECTED]> wrote:
>
> Sorry for bringing up an old post...If you have a generic set of tables..
>
> eg. table of countries / post codes etc which are used across several
> databases what is the best way to access / store them?
> I currently
> -
Hermann Muster wrote:
> Bill Moran wrote:
>> In response to Hermann Muster <[EMAIL PROTECTED]>:
>>
>>
>>> Hello everyone,
>>>
>>> I already asked about that a couple of days ago, but didn't get an
>>> satisfying solution for my problem which is following:
>>>
>>> I need to create a view that
On Thu, Jul 3, 2008 at 7:29 AM, Hermann Muster <[EMAIL PROTECTED]> wrote:
>
> I just found the time to try that out and it worked! Thank you for your
> help. I actually had no idea about using schemas in PostgreSQL. It was easy
> to setup and db_link isn't needed anymore. I hope I won't run into an
Bill Moran wrote:
In response to Hermann Muster <[EMAIL PROTECTED]>:
Hello everyone,
I already asked about that a couple of days ago, but didn't get an
satisfying solution for my problem which is following:
I need to create a view that does a query on a second database on the
same Postg
On Fri, Jun 20, 2008 at 8:06 AM, Bill Moran
<[EMAIL PROTECTED]> wrote:
> In response to Hermann Muster <[EMAIL PROTECTED]>:
>
>> Hello everyone,
>>
>> I already asked about that a couple of days ago, but didn't get an
>> satisfying solution for my problem which is following:
>>
>> I need to create
In response to Hermann Muster <[EMAIL PROTECTED]>:
> Hello everyone,
>
> I already asked about that a couple of days ago, but didn't get an
> satisfying solution for my problem which is following:
>
> I need to create a view that does a query on a second database on the
> same PostgreSQL serve
Hi, Hermann.
The best solution in my opinion would be using users name and password
to connect to database. That way you can decide (grant) what tables can
be accessed by this user and there is no password you have to hide from
him (or others). So use stored procedure returning set of records
Hello everyone,
I already asked about that a couple of days ago, but didn't get an
satisfying solution for my problem which is following:
I need to create a view that does a query on a second database on the
same PostgreSQL server. dblink seems to be the only (???) solution for
doing so. The
11 matches
Mail list logo
