Closed rizqidjamaluddin closed 9 years ago
sqlite was the first driver i supported when writing the configuration update. Did you provide a host in your configuration? Which branch are you running off of? Neither master or develop have line 143 that pertains to such an issue.
I'm on 0.4.3 as per suggested constraints for installation on the readme. The line in question is this one, and no, I didn't provide a host in the sqlite configurations because it's not a key in laravel's config, nor is it a key in doctrine's config.
I can try upgrading to 0.5.x and try again. It looks like the driver mapper stuff should fix this issue.
Ahhh. Try one of the newer versions/dev. sqlite wasn't property supported back then :)
Is 0.5.x stable enough to use in general? I haven't installed it just yet, but it does look like it'll fix the issue.
It should be fine. Quite a few of us are using it in big projects atm, it's just that it's ongoing with lots of extra features/requirements coming.etc, so it can be unstable. Test, if it works - awesome :)
We should wrap it up when L5 is released.
Yep, looks like it. Thanks for the help! :)
The pdo_sqlite driver doesn't work because the service provider is trying to grab values from nonexistent array keys (which are irrelevant for sqlite). Trying to use an sqlite driver raises
Undefined index: host
from LaravelDoctrineServiceProvider.php:143.Maybe a simple if/else for now, as sqlite seems to be the odd one out?