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
The need to manage the scheme of sqlite database is quite clear. op-sqlite started just as a low -level layer to interact with sqlite but more and more people are using it as their main interface. I don't want to write an ORM, ORMs are just overhead for some convenience around objects (IMO) but there are quality of life features we can do that will just repeat in every project.
Migrations is one of this features. Writing your SQL by hand is fine, but keeping track of which migrations have been applied and applying them on app start is a low hanging fruit we can bake in into op-sqlite and solve the problem for everyone.
The text was updated successfully, but these errors were encountered:
What do you need?
The need to manage the scheme of sqlite database is quite clear. op-sqlite started just as a low -level layer to interact with sqlite but more and more people are using it as their main interface. I don't want to write an ORM, ORMs are just overhead for some convenience around objects (IMO) but there are quality of life features we can do that will just repeat in every project.
Migrations is one of this features. Writing your SQL by hand is fine, but keeping track of which migrations have been applied and applying them on app start is a low hanging fruit we can bake in into op-sqlite and solve the problem for everyone.
The text was updated successfully, but these errors were encountered: