i need to make a new instance of Product, what do i pass to menus? what i have now for example - is [1,2,3] which is the IDs of the menus, Menu[1] etc. do i need to explicitly do menus=[Menu[n] for n in menus] in order to get the Menu instance, or passing menus=[1,2,3] is enough?

i prefer to pass IDs list since that's what i got

Currently direct using of IDs is not supported, you need to load object first. This way Pony can be sure that the object with this ID is actually presented in the database.

Hi, you can write raw SQL fragments with array_length and json_object_keys like in this example: https://stackoverflow.com/a/36173097/1706814

What do you mean?

I just did Menu[1].delete() flush() And i got pony.orm.core.OperationWithDeletedObjectError: Menu[1] was deleted

Can you show a traceback?

What is impossible?

These are bots

Currently db_session has limitations when used with async functions: 1) don't use db_session as a decorator with async functions, use with db_session inside async function instead 2) Never call async functions inside db_session, only normal function calls are possible

async def my_function(): f1() await f2() # you can use await here with db_session: f3() # only usual function calls are allowed here f4() await f5() # await calls a possible outside of db_session scope with db_session: f6() # only usual function calls are allowed here It is not very convenient, especially considering the fact that you cannot create pony object in one db_session and use it in another db_session, but currently it works this way

> What’s wrong with that It is possible. But this is the same as async def f(): with db_session: thing = database.MyEntity() await async_f(ABC, thing) Which is also possible. But this will not work: async def f(): with db_session: thing = MyEntity.get(id=123) await async_f(ABC, thing) async async_f(something, thing): print(thing.foo.bar.baz) Because when you do MyEntity.get(id=123) it loads the thing itself and its direct attributes (thing.foo), but not related objects like think.foo.bar, it requires additional SQL queries. And queries are possible only inside db_session. So, if you need access thing.foo.bar.baz later, you need to load it inside the original db_session: async def f(): with db_session: thing = MyEntity.get(id=123) thing.foo.bar.baz # force loading from the database await async_f(ABC, thing) async async_f(something, thing): print(thing.foo.bar.baz)

No, it will not work this way. The actual session cache object is created internally and tied to the current thread. db_session was not developed with async approach in mind, and needs to be reworked to be used with async

and how to do this when a async is in a for loop with a db session and a await function?

Pony was not developed for async usage, and it may be tricky to use it correctly in async environment. The best way is to have dedicated thread for database access and communicate with it through queues. > and how to do this when a async is in a for loop with a db session and a await function? I don't know what specifically you mean, but it may be something like: async my_function(): for item in items: with db_session: objects = access_database() data = [obj.to_dict() for obj in objects] await another_async_func(data)

Pony does not have direct support for GIS, but you can add raw SQL fragments to your queries

Pony does not have direct support for GIS, but you can add raw SQL fragments to your queries

On an unrelated side note, my 65-yo-mum looked at my screen earlier and remarked how "nice and orderly" the db diagram in the pony editor looked. She's anything but a tech person. I don't know where it came from, but I think this compliment belongs to you, @alexey115

I think what you want is called dumping?