HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Based on the comments made here, categorizing the idea as "already exists"
Sorry but I still don't get why the example have to be coded with relational database design. You can still have those two "master tables" as non relational tables and reference them in your "transaction tables"
Document locking is possible in Domino but this get very tricky if your application reside in multiple servers.
Unique value is possible (@Unique) should do the trick. Running number is a bit more complex but can still be done as long as the document readers is not restricted.
Prohibit to delete master is handled a bit differently, usually this would mean that you need to code your archive process so that it remove a master and all transaction that reference said master to the same place (NSF). This is because document is rarely deleted in Domino except for archiving purpose.
Thank you very much for your response to my idea,
I understand the difference of type of products. Of course, I also understand the goodness of non-relational database like Notes.
Most of the users require to make their system which has table designs with work flow etc.
For example, their product information about law in chemical industry. This has two master tables. The result data of the product information use two master when users register. Finally, using work flow for open to public users in the company.
In this case, Now that we have to make some codes originally for the master when we use Notes. But relational database can control its definition. Of course, relational databases also have a couple of week points.
In my opinion, If Notes has tables in NSF, we can easily develop business application more and more and increase user's satisfaction.
Finally, Our user wouldn't like to use relational database without data registration.
You'd know what the reasons are.
Best regards,
I am confused, Notes is supposed to be a non-relational DB and yet you wanted it to behave like a relational DB ? Can you explain in more detail what is the use case for this ?