You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently we've been asked to move our Laravel app into a new infrastructure where all applications with a oracle database use Oracle's Edition Based Redefinition.
Has anyone else been able to use this plugin and support the feature?
-->
My idea on how to implement the feature
The basic principle of Edition Based Redefinition is that you put all your views, triggers and other bits into a edition (not table or sequences). To then access any of them you need set your session edition first like:
ALTER SESSION SET EDITION = *EDITION NAME*;
So I was thinking maybe we could create a new config called EDITION and then when the connection is made to the database run the above SQL with the config value before performing any actual SQL.
I haven't had a deep dive into the code to see where this connection is made as wanted to see if someone has already solved this issue. If no-one has any chance someone could give me an idea on where to start and I'll start work.
-->
System details
Oracle Version: 12c
PHP Version: 7.2
Laravel Version: 5.6
Laravel-OCI8 Version: 5.6
Thanks in Advance.
The text was updated successfully, but these errors were encountered:
@Adam2Marsh this is the first time I heard about edition. Making a quick search on it and seems like we just need to alter the session as you mentioned. In this regard, I think your proposed solution might work. You can start on Oci8ServiceProvider to modify the session. Thanks!
Summary of problem or feature request
Recently we've been asked to move our Laravel app into a new infrastructure where all applications with a oracle database use Oracle's Edition Based Redefinition.
Has anyone else been able to use this plugin and support the feature?
-->
My idea on how to implement the feature
The basic principle of Edition Based Redefinition is that you put all your views, triggers and other bits into a edition (not table or sequences). To then access any of them you need set your session edition first like:
So I was thinking maybe we could create a new config called
EDITION
and then when the connection is made to the database run the above SQL with the config value before performing any actual SQL.I haven't had a deep dive into the code to see where this connection is made as wanted to see if someone has already solved this issue. If no-one has any chance someone could give me an idea on where to start and I'll start work.
-->
System details
Thanks in Advance.
The text was updated successfully, but these errors were encountered: