Document using SQLAlchemy column types; add pydantic.EmailStr support

[rmasters]

When I start a new project, I typically start with a User model and always bump into this error:

ValueError: <class 'pydantic.networks.EmailStr'> has no matching SQLAlchemy type

Today I decided to dig into this, and found that EmailStr doesn't subclass str, which explains why it needs a Field(sa_type=String()). I noticed the AutoString types for ipaddress & pathlib, and figured EmailStr might be popular enough to be worth adding (example discussion).

As part of this, in order to test that change I've started documenting how SA column types work in SQLModel. I also noticed the mention about varchar length and documented that too.

Let me know if you'd prefer this as two separate PRs and I can cherry-pick it out - they're only together as I wanted to use the docs-tutorial tests (which are awesome!)

---

• Add pydantic.EmailStr support to get_sqlalchemy_type
• Add documentation for column types, including varchar/text string lengths
• Finish testing "exotic sqlalchemy type" (geoalchemy2) tests
  • I originally had some test cases for GIS using geoalchemy2's SQLAlchemy column types. Testing this with sqlite requires libspatialite, which probably needs some CI work/containerization to add this to the environment. I'll revisit this as a separate advanced tutorial in another PR if there's interest.
• Finish testing ipaddress, pathlib & EmailStr AutoString type alises
• Rebase commits to a clean history

[github-actions]

📝 Docs preview for commit 8bd9068 at: https://23112ba0.sqlmodel.pages.dev

[github-actions]

📝 Docs preview for commit 0e8c5bc at: https://cb2b259d.sqlmodel.pages.dev

[rmasters]

I was surprised to find sqlmodel/pydantic don't convert these values to string for persistence or back into the IP/Path types on retrieval. I think the solution is to implement a Pydantic type, but perhaps I'm doing something wrong here?

[bschoenmaeckers]

I think this is a bug in the pydantic v2 implementation because it used to convert it back to native python types. I've seen it happen with datetimes as well.
Edit: never mind, this has been a problem for quick a while.

[github-actions]

📝 Docs preview for commit 7aead7f at: https://f76c7357.sqlmodel.pages.dev

[github-actions]

📝 Docs preview for commit bae753d at: https://c988b4c3.sqlmodel.pages.dev

[github-actions]

📝 Docs preview for commit 8cd7c17 at: https://2b2d516a.sqlmodel.pages.dev

[github-actions]

📝 Docs preview for commit 8c45261 at: https://8390b32c.sqlmodel.pages.dev

[github-actions]

📝 Docs preview for commit 9a0c172 at: https://fe6eeaf3.sqlmodel.pages.dev

[mockingjet]

Any update on this MR?

[nameer]

Bump! This is much needed