Re: public synonym

You can infer the context by first setting the search_path variable.  You can set it initially in your connection or do it for a database context or even a role context
SET search_path = MASTER_USER, public, pg_catalog;
ALTER DATABASE whatever  SET search_path = MASTER_USER, public, pg_catalog;
ALTER ROLE whoever SET search_path = MASTER_USER, public, pg_catalog;

Then you can continue to let the tables be non-qualified.   bye bye synonyms!

Regards
Michael

Eugene Yin

Thursday, January 7, 2016 3:17 PM

PostgreSQL ver 9.4.5.  Linux OS.

Application:  Web Based

Platform:  

    App Server (java) --> jdbc call --> Database Server (PostgreSQL)

I do know that PostgreSQL does not support the public synonym.  Now, for a user schema (let's call it MASTER_USER), if I coded in the stored function/procedure like the following, without using a public synonym to identify the table name: 

select user_name from user_info_table

then access it from the Java (web app) side via the JDBC call to the database, will that work?  

OR, 

I must use the identifier inside the sql, such as:

 select user_name from  MASTER_USER.user_info_table?

I come from the Oracle world, there I first create the public synonym for the table, then in the stored procedure I just directly reference the table with no need to identify the table with a schema name.  Like to know how it work under the PostgreSQL.

  

Thanks

Eugene