When Velo users start to write more complex applications, they almost automatically shift from datasets to wix-data. But …, writing robust queries, inserts, etc is more complex than the wix examples show.
Ahmad and I have been talking about this earlier, that we (Masters) are basically developing almost the same functions over and over again to deliver real world apps that do not blow up in your face at the first error or time-out.
We are thinking of developing a framework (with code) on Github, which offers a layer over wix-data which anybody could use in their own projects. We will need help from wix (error codes) and from other Masters, but first we would like to know if there is any interest in such a framework.
So Ahmad has added a tutorial request on his site. If you think this is a good idea, you can vote here:
https://www.nasriya.net/tutorial-request/robust-data-handling-framework
9 Likes
Interested, and willing to commit (pun intended) to the repo and review code
Keep this idea alive. Good idea.
Very interessted to take a look on your RESULT-FRAMEWORK.
Working on something similar to your idea…
https://www.media-junkie.com/pflegeservice
My idea was almost the same. Do not wanna do all that coding over and over again.
Tryed (trying) to develop something more comfortable and easy to use with a lot of features and flexibility (but in a form of a tool.)
I’m on the fence. It’s not clear to me that building a framework on what is essentially already a framework is efficient. Frameworks restrict creativity and often dumb down users’ knowledge and incentive to learn what lies underneath the framework.
What examples supporting this do you have? Errors always happen in code and have to be handled. Many Velo implementations I have seen don’t have great error handling.
If you have the code already perhaps share it to GitHub first. Then encourage support and contribution. If what you have is valuable you will get support.
I am struggling with dataset and wix-data … I like the idea but I am also weary of third party open source things that may have limited impact - I am trying to guard your time.
It would be nice to really have basic case book, list of good advisors, etc. This community needs help not guessing.
After working for several months using Velo (including wix-data), I think the framework is great to get the user up to speed to create basic functionalities. It hides the complexity of managing databases and interfacing between components. However, the framework is still too weak for heavy and serious use cases. For example, I have just stumbled to the issue that wix-data doesn’t seem to provide any concurrency control, such that, you may face race condition when two or more actions updating the same entry of dataset at the same time.
https://www.wix.com/velo/forum/community-discussion/atomicity-when-updating-a-field-in-collection
So in my opinion, it is better to first drive wix-data to become more mature, than to create another framework on top of it.