Arjay Angeles
Arjay Angeles
Also, the error `ORA-00942: table or view does not exist` clearly states that the object you are accessing is not available on your connection. That should be a hint that...
Hmm, that's odd. My projects also uses multiple connections and multiple schema in same connections and does not have any problem at all. I even have a mixed connections of...
I just tried this on Laravel 5.8 and all works fine. ```php Schema::create('studies', function (Blueprint $table) { $table->bigIncrements('id'); $table->string('exclude_study_number'); }); >>> DB::table('studies')->insert([ 'exclude_study_number' => 'C94043-01' ]) => true >>> DB::table('studies')->get()...
Seems like an environment issue. See https://github.com/yajra/laravel-oci8/issues/506 for some solutions.
I think since Laravel 5.4, setFetchMode support was already removed by the framework itself. See https://laravel.com/docs/5.4/upgrade. BTW, please report on the oci8 repo. Thanks! > Fetch Mode Laravel no longer...
Haven't encountered a similar issue yet. Can you please provide snippets to reproduce the issue?
@mohd-aidi were you able to install the required doctrine package as per laravel [docs](https://laravel.com/docs/5.5/migrations#modifying-columns)?
Will try to replicate this later if I can.
Can you please provide some snippets to reproduce the issue that this PR fixes? Or some tests would be better if possible. Thanks!
@jokeronaldo you might be using a global scope somewhere in your code that adds the null sql?