Allowing integer to map to i64 for sqlite

[Boscop]

When I use id integer not null primary key autoincrement in sqlite, I have to use i32 in Rust but I want to have i64 because I have a lot of records, but when I write id bigint not null primary key autoincrement I get:

error: AUTOINCREMENT is only allowed on an INTEGER PRIMARY KEY

This is a syntactic limitation of sqlite but sqlite stores all integers as arbitrary precision anyway, so it would be possible for diesel to also allow mapping integer to i64.
It would be very useful!

Also, it doesn't let me use u64 for size_bytes unsigned bigint not null, only i64...

[sgrif]

This has been raised before, and we decided to keep things as they are for reasons I laid out in #852 (comment). If you need i64 keys, you can use table! or diesel print-schema and specify that the id column is of type BigInt there, but I don't think we should change the behavior of schema inference for the reasons I laid out in the previous comment.

[WANG-lp]

@sgrif Very glad to see there is a correct method to use i64 for Sqlite.

I think #80 can be also solved this method.

Maybe we can collect similar questions and solutions to a separated Wiki page to help newcomers!