Added schema parameters to functions in join and select

[skytz]

• also bumped the version number to ilustrate the changes

[kurtbuilds]

Hey, sorry I thought I already left a comment on this.

Most people are going to infrequently, if at all, use schemas.

Because of that, I don't think it makes sense to have most people pass a None parameter, which would cause confusion.

Few possible workarounds:

1. The functions take an S: Into<Table> or something, which &str would implement. Strings could get parsed to split schema if there's a ..
2. Adding secondary convenience methods like from_table_with_schema

Something else?

[skytz]

I'm not a big fan of magic strings, so the first approach was too close to that for me.
The only good solution for me would be the 2nd one, with "with_schema" at the end. It's explicit.
I've also reverted all the formatting issues.

[kurtbuilds]

Two small comments. Once that's done, happy to merge & cut release.

[kurtbuilds]

For 0.x, the 2nd number is a major version.

Since this is just adding names, I think this can just be a minor bump. 0.11.5. (if it is breaking, the next version would be 0.12.0.)

That said, I'm happy to bump version for a cut after merge.

[skytz]

yeah, you're right, it doesn't break compatibility, it did before the added functions

[kurtbuilds]

One adjustment I'd make: since the function explicitly is called _with_schema, I think it makes sense to take a &str instead of Option<&str>.

Likewise for the other method names.

[skytz]

the problem with taking a &str is that in external calls (specifically in ormlite)..you need to have an if or a match to check for schema when creating the objects, in all cases. It's a bit...ugly.
I'm ok with either one, you pick.