I've never had a need to have it set in the connect string because our
logon trigger sets it for us based on a variety of criteria.
execute immediate 'ALTER SESSION SET CURRENT_SCHEMA = SOMESCHEMA';
Matt
On Mon, Nov 12, 2012 at 1:04 PM, Martin J. Evans
<martin.ev...@easysoft.com>wrote:
> Hi Kevin,
>
> I've forwarded your email on to the dbi-users list. See
> http://dbi.perl.org and look at the support page. Sorry for top posting
> but my email client is having some sort of fit with your email. I don't
> have any issue with any well formed patch to set the schema but I'll wait
> to see what others say as personally I've never had to change it.
>
> Martin
>
>
> -------- Original Message --------
> Subject: DBD::Oracle Schema different than User question
> Date: Mon, 12 Nov 2012 13:04:05 -0500
> From: Kevin L. Kane <kevin.k...@gmail.com>
> To: Tim Bunce <t...@cpan.org>, Yanick Champoux <yan...@cpan.org>,
> "Martin J. Evans" <mjev...@cpan.org>
>
> Hi all,
> I am running into a problem and was planning on modifying my local
> DBD::Oracle to add support for a "schema=<mySchema>" construct in the
> connect string. Specifically, I want to connect as user X but set
> current_schema to Y. Another solution i've toyed with is having a
> trigger that switches my schema when I log in but I need to do this
> for a lot of different schemas and I will always be the same user. It
> seems weird to me that support for this isn't included in DBD::Oracle
> currently.
>
> If I do this in a sane way are you at all interested in the patch? Am
> I just missing something and this functionality is already there? Or
> should this functionality not exist in the first place and why?
>
> Thanks,
> Kevin
> --
> Kevin L. Kane
> kevin.kane at gmail.com
>
>
>
>
>
>
>
