Hello
2013/10/10 Kalai R
> Hi,
>
> I am developing .Net application using PSQL. I am using npgsql to connect
> PSQL database. In single database I have more than one schemas. After I
> connect database I set search path using "Set Searchpath command" for the
> required schema. It works perfectl
Hi,
I am developing .Net application using PSQL. I am using npgsql to connect
PSQL database. In single database I have more than one schemas. After I
connect database I set search path using "Set Searchpath command" for the
required schema. It works perfectly.
But after sometime, I need to change
chiru r writes:
> Is there any schema(set search_path) behaviour changes from PostgreSQL9.1
> to PostgreSQL9.2 ?
Please read the release notes when updating to a new major version.
The first item under "Server Settings" in the 9.2 release notes is:
Silently ignore nonexistent schemas sp
> postgres=# select version();
> version
>
>
> ---
> PostgreSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2
> 20080704
Hi All,
I have seen strange behaviour in PostgreSQL9.2 version,it has been allowing
to set search path any name,even the name is not created as a schema in
database.
Please find the below case between PostgreSQL9.1 and PostgreSQL9.2.
*PostgreSQL9.2:*
+
postgres=# select version();
On 14/09/2010, at 8:56 AM, Tom Lane wrote:
Bruce Momjian writes:
Yaroslav Tykhiy wrote:
SELECT * FROM foo.bar WHERE bar.a=1;
^^^ this means foo.bar
Do you think it's a feature or a bug? :-)
Feature, and SQL-standard behavior.
It might be worth pointing out t
Bruce Momjian writes:
> Yaroslav Tykhiy wrote:
>> SELECT * FROM foo.bar WHERE bar.a=1;
>> ^^^ this means foo.bar
>> Do you think it's a feature or a bug? :-)
> Feature, and SQL-standard behavior.
It might be worth pointing out that this has nothing to do with
search_
Yaroslav Tykhiy wrote:
> Hi there,
>
> Sorry but I've got yet another issue to discuss today, this time that
> on schema search path. In fact it may not be a bug, but it may be
> worth a note in the documentation.
>
> It seems that if the table in SELECT FROM has an explicit schema
> speci
Hi there,
Sorry but I've got yet another issue to discuss today, this time that
on schema search path. In fact it may not be a bug, but it may be
worth a note in the documentation.
It seems that if the table in SELECT FROM has an explicit schema
specifier, further references to the same
