Roadmap

[dantownsend]

Discussing the future direction of Piccolo.

[dantownsend]

Some good suggestions made by @heliumbrain #10 (comment)

I've started creating some GitHub project boards, for organising enhancements and bugs.

I'll retire the roadmap issue, and use this discussion thread instead. Any ideas listed there will be turned turned into issues, and will add them to the enhancements board.

[aminalaee]

@dantownsend Here some random ideas:

• Support for PK UUID ( I can pick that up)
• PostGIS support ?
• Random model builders for testing (there's usually a side-project like django model-bakery or blender) but that can be in project
• Pydantic validation
• Abstract tables for inheritance

[aminalaee]

I played around the UUID primary key a bit.
Since we're creating table.id as PrimaryKey, id = UUID(primary=True, key=True) doesn't work. We add id by default as Integer or Serial to be more precise and overrides any other Primary Key.
I started working on a PR to add support for any column as Primary Key, I think I can get that out in a few days.
I'll also create an issue to discuss the approach.

[dantownsend]

Great, thanks!

[aminalaee]

@dantownsend What do you think about having some more managed fields/tables.
For example I've seen GORM in Go provides the ability to have a somewhat managed models where it can automatically add created_at, updated_at, even deleted_at for soft-deleting models.
I'm thinking something like class MyTable(Table, managed=True) can do that.

[dantownsend]

@aminalaee It's a nice idea. I wonder how descriptive managed is though - perhaps it could be called something like auto_timestamped?

[aminalaee]

Yeah, that's better.