Re: Problem in "Set search path"

From: Alban Hertroys <haramrae(at)gmail(dot)com>
To: Kalai R <softlinne(dot)kv(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem in "Set search path"
Date: 2013-03-21 16:12:20
Message-ID: CAF-3MvOK-hX8DnbDTKJ5=7D2ews3m=edqheUeCfb17ShDQVUKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 21 March 2013 16:59, Kalai R <softlinne(dot)kv(at)gmail(dot)com> wrote:

> Hi,
> Thanks for ur suggestions. I create connection from my .net application
> and set search path by single query. After set search path I call psql
> function from my .net application using the same connection. In this case
> some time search path set but some times not. I didn't use prepare
> statement.
>

Is that the same connection object in ,NET or the same connection to a
connection pool or the same database connection? That's not necessarily the
same.

Do you still have this problem if you set the search_path at the start of
your transaction?

Did you know you can set a search_path on user (role) objects and on
database objects in the database? That might just take out your need to
specify it in your ,NET application.
--
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Cristian Cruz 2013-03-21 17:53:48 Re: Bad plan on a huge table query
Previous Message Adrian Klaver 2013-03-21 16:04:39 Re: Problem in "Set search path"