You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can very quickly become non-Light, and maybe it shouldn't be actually done, but it might be useful to have a simple notification center that can broadcast DB change notifications.
I had the feeling that it is better to let the user do this in own code as required.
I'd probably do this as a simple closure the user can hook up to anything he wants, like:
MyDatabase.onChange{ some enum in}
It quickly becomes a Pony, users might want to know the exact tables or IDs affected and so on, which sometimes isn't even possible w/ SQL itself.
Transactions also complicate the matter.
Maybe rather something for Heavier. So a basic mechanism might be helpful.
The text was updated successfully, but these errors were encountered:
Since that callback gives the table id, and is called once for each changed rowid, it could associate changes with tables/views nicely and even group rowids together per transaction.
This can very quickly become non-Light, and maybe it shouldn't be actually done, but it might be useful to have a simple notification center that can broadcast DB change notifications.
I had the feeling that it is better to let the user do this in own code as required.
I'd probably do this as a simple closure the user can hook up to anything he wants, like:
It quickly becomes a Pony, users might want to know the exact tables or IDs affected and so on, which sometimes isn't even possible w/ SQL itself.
Transactions also complicate the matter.
Maybe rather something for Heavier. So a basic mechanism might be helpful.
The text was updated successfully, but these errors were encountered: