| From: | Naveen Kumar <naveenchowdaryon(at)gmail(dot)com> |
|---|---|
| To: | Mayank Gupta - Network <gupta_mayank2(at)network(dot)lilly(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org>, Vikram Chaudhary - Network <chaudhary_vikram(at)network(dot)lilly(dot)com> |
| Subject: | Re: Need help in making the schema name case insensitive. |
| Date: | 2017-12-07 11:29:50 |
| Message-ID: | CADk76jrDHnsshjAsR5qeL02mEDN8p-uA=OMDc1hatygEOuTNdg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
No need to drop and create. You can
ALTER SCHEMA name RENAME TO new_name
Regards,
On Dec 7, 2017 4:48 PM, "Mayank Gupta - Network" <
gupta_mayank2(at)network(dot)lilly(dot)com> wrote:
> Hello Team,
>
>
>
> We need your assistance in below scenario.
>
>
>
> *Scenario:* We have a case sensitive schema name (e.g “Schema_Name”), due
> to this reason we have to put schema name in double quotes. Now, we have to
> connect the postgreSQL server via “informatica on cloud”. For the
> connection from informatica to Postgress we are using *JDBC* connection.
>
>
>
> *Problem:* While connecting to the server via JDBC connection,
> “Informatica on cloud” do not take case sensitive schema names due to which
> we are not able to fetchtables from the schema. Could you please suggest
> any alternative solution that can either give non-case sensitive *alias*
> to our case sensitive schema or how to make our schema case insensitive.
>
>
>
> *Note:* The existing schema is old schema so we don’t have the option to
> *drop* *and re-create* new schema.
>
>
>
> Regards,
>
> Mayank
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mayank Gupta - Network | 2017-12-07 13:03:09 | RE: [EXTERNAL] Re: Need help in making the schema name case insensitive. |
| Previous Message | Mayank Gupta - Network | 2017-12-07 09:50:31 | Need help in making the schema name case insensitive. |