issue_comments

Reminder: the current list of arguments for those methods is: https://github.com/simonw/sqlite-utils/blob/13528faa817d79bc3900d3af7473300686b145d7/sqlite_utils/db.py#L951-L967

The syntax for explicitly creating a table looks like this: python db["cats"].create({ "id": int, "name": str, "weight": float, }, pk="id") So using a dictionary of column name -> Python type here would be good.

I think it becomes a new optional argument to .insert_all() and .insert() and .upsert_all() and .upsert(). Question is, what should that argument be called?

Options:

• columns
• types
• type_overrides
• extra_columns

I like the first two best. I'm leaning towards columns - it would serve two purposes: you can use it to ensure extra columns are created, and you can use it to specify the type on extra OR deteced columns.

Maybe something like this:

python db["authors"].insert_all( [{"id": 1, "name": "Sally", "score": "2"}], pk="id", not_null={"name", "score"}, defaults={"score": 1}, columns={"score": int, "weight": float} )

Documentation here: https://sqlite-utils.readthedocs.io/en/stable/python-api.html#listing-rows

Released in 2.6

I think a neat way to do this would be with an optional argument for .rows_where():

python rows = db["table"].rows_where("age > 10", order_by="age desc")

If you want everything you can use this:

python rows = db["table"].rows_where(order_by="age desc")

It's a tiny bit weird calling .rows_where() without a where clause, but I think it makes sense here - especially since .rows is a property that can't take any arguments - though under the hood it actually does this:

https://github.com/simonw/sqlite-utils/blob/ad6ac19470a67867b96cb4c086450b8e4e46bf02/sqlite_utils/db.py#L436-L443