Arjay Angeles
Arjay Angeles
`debug_backtrace` hack was added I think on v5.1 and was not updated maybe since 5.5. Maybe there is a change on the object arrangement on Laravel 5.2 that causes this...
> It seems to me that the laravel application, rather than picking up the first ID in ascending order, takes any random ID at the time of generating Sequence (DB...
Can you please provide a working script to replicates the issue?
I am not yet familiar with named parameters but based on your example, maybe using raw sql may do the trick? ```php $bindings = [ DB::raw("first_thing => 'Number 1'"), DB::raw("second_thing...
Can you please provide the error dump on logs?
Just fetch the next sequence value. See https://yajrabox.com/docs/laravel-oci8/master/sequence for ref.
Just found out while working on #615 that there is a failing test for this scenario. Will try to fix on future release. Thanks!
As the error suggested, double check that there are no existing records that violates the unique constraints.
Not sure on codeigniter integration but it can be used outside laravel afaik. See https://yajrabox.com/docs/laravel-oci8/master/stand-alone for ref.
Oracle has a 30 char limit on object names. Given this, you need to manually set the constraint name or upgrade to Laravel 5.6 version if possible. This was addressed...