Welcome to the #dominoforever Product Ideas Lab! 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 jointly by the IBM & 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.


Add a relational database

Domino does quite well with document oriented data. But handling tabular data is a real pain. It would be VERY usefull if we were able to create SQL tables. I used H2 in several projects. But this way SQL data is stored outside the NSF and only accessible locally. Would be much easier to handle if the data was inside the NSF and could be accessed via NRPC. It would be even nicer if the SQL data would raplicate - but even without replication several projects would be much easier to implement.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 16 2018
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    October 17, 2018 03:05

    First of all I am assuming that you tabular data is relational (since most of tabular data I handled are not relational). You do have several options like NotesSQL / LEI / ODBC to read the data from Notes but all of them are quite old and not developed further. Maybe there is a more recent 3rd party solution out there that can replicate between relational and non-relation db ?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    October 18, 2018 10:33

    My point is tabular data. Let's say statistics. Very simple data but thousands of rows each day. Sometimes we have to deal with that kind of data in Notes. But it's a real pain to even store it in Notes. NotesSQL, LEI and DECS don't help a bit with that. And if it comes to relations between tables things get even worse. We could very nicely have our code in Java agents and store and process data in H2. But no clients can access a H2 database on a server (yes, of course they can. But that needs opening ports on firewalls and implementing security layers)

  • Admin
    Thomas Hampel commented
    October 19, 2018 13:51

    Would Domino Query Language be an option?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    October 19, 2018 14:15

    "Would Domino Query Language be an option?"

    No. Because DQL is used to deal with data in Notes documents. The data I'm talking about does not fit in documents - mainly because there are too many rows/documents. One example is logging: Our application log holds > 1,000,000 documents (in dev, not production!). Most of these documents hold multiple log messages. It's a pain to rebuild a view index. And counting all messages of a certain type is impossible.

    If we had some kind of rudimentary DB/2 build into Notes/Domino such task would be a no-brainer. 100 million log records are nothing for any relational database, are they?

    Of course we could use any stand alone SQL-DB for that. But convincing decision makers of that is impossible in most projects.

  • Admin
    Thomas Hampel commented
    October 27, 2018 07:45

    Moving to Domino Designer category