RatkoR

Ahh, I see you already have a similar PR open: https://github.com/muesli/cache2go/pull/61/files. I'm fine if you merge #61 and close my PR.

Yes, I've got to this one also. What I did is I created migration table manually and then didn't think about it any more. I can't just remove the exception....

> Shortly speaking, don't merge this. Ok, I'll keep the PR open so that I don't forget about this problem. Thx!

Yes, you're right. Currently we connect to the default `doc` schema. I'd welcome a PR that adds this. Just do what you did in your example but with `isset()` test...

Strange.. Please paste or send me your setup (composer.json). I cannot get this error with the codebase I have. I added prepared statement [tests](https://github.com/RatkoR/laravel-crate.io/blob/master/tests/DataTests/DataTest.php#L261) and I'm passing both of them.

I'm still not getting this error. If your app is just a startup project or if you can extract the error test case route and model, would you be willing...

Try it without the debug bar. DebugBar tries to show the full SQL query with all parameters quoted inside the SQL - it changes prepared statement into a complete SQL...

@JulianMar knows about [Crate.io driver for Laravel](https://github.com/RatkoR/laravel-crate.io), he has contributed much to it. I'd also be interested in moving dbal to newer version.

No, unfortunately not. Instead of loading users with dataloaders, we load them together with todo items.