Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upsqlite connection error? (title updated) #224
Comments
This comment has been minimized.
johalun
commented
Feb 20, 2016
|
Ok, so just specifying a file as DATABASE_URL "diesel setup" and "diesel migration run" generates a database correctly but when I try the write_posts/read_posts (which works with pgsql) I get connection error: [mirama@PC1-13-0006 diesel_demo$ cargo run --bin write_posts note: Run with RUST_BACKTRACE=1 for a backtrace.Process didn't exit successfully: target/debug/write_posts (exit code: 101)
|
johalun
changed the title from
sqlite backend?
to
sqlite connection error?
Feb 20, 2016
johalun
changed the title from
sqlite connection error?
to
sqlite connection error? (title updated)
Feb 20, 2016
This comment has been minimized.
johalun
commented
Feb 20, 2016
|
Oh I see.. I have to use different API for sqlite :) That brings us to the next problem. infer_schema!() is not implemented for sqlite. What is the way to solve this with sqlite? |
This comment has been minimized.
|
Hi @yohanesu75! You can definitely use a sqlite backend. The CLI figures out what backend to use based on your DATABASE_URL, which is why it correctly used SQLite. I'm pretty certain that the getting started demo is written all using Postgres, so a lot of it won't be compatible. It looks like you figured out to use the |
This comment has been minimized.
|
You need to call |
sgrif
closed this
Feb 21, 2016
This comment has been minimized.
johalun
commented
Feb 21, 2016
|
Thanks! Sent from my iPhone
|
johalun commentedFeb 20, 2016
Hi! First of all, thanks for great job!
How can I change to sqlite backend? I can't find any documentation about this.