Re: Problem in "Set search path"
| От | Alban Hertroys |
|---|---|
| Тема | Re: Problem in "Set search path" |
| Дата | |
| Msg-id | CAF-3MvOK-hX8DnbDTKJ5=7D2ews3m=edqheUeCfb17ShDQVUKQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Problem in "Set search path" (Kalai R <softlinne.kv@gmail.com>) |
| Список | pgsql-general |
On 21 March 2013 16:59, Kalai R <softlinne.kv@gmail.com> wrote:
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.
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.
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.
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.
В списке pgsql-general по дате отправления: