nuBuilder Forum

Developers are always ambitious, so they embark on the development of increasingly large projects. For this reason, they don't want to invest years of work on a platform that won't allow them to do that. I see an inconvenient limitation with nubuilder, since nuBuilder does not support transactions in the database. Does the development team plan to change something?

Correct, nuBuilder does not support transactions in the database. However, in my experience, even with hundreds of forms and users, I have not encountered any integrity issues in the past. If there is a necessity for transactions, we gladly accept any pull requests.

How acceptable is the strategy, which had a memory variable on the form, whose changes would then trigger a built-in procedure that would update several tables within the transaction?

Yes, this is certainly feasible if you execute a nuBuilder Procedure. However, the question is whether the update should be carried out every time a change is made.