根据唯一字段值链接两个不同的 Lotus Notes 数据库
我正在开发两个应用程序的应用程序 - “员工数据库”和“日历数据库”。
我需要链接两者 - 以便单击“员工数据库”中的员工，然后在“日历数据库”中查找他们的所有信息。
该链接将由该人的 UNID 建立，可在两个数据库及其各自的表格中找到。
如果我用 SQL 写这个，大约需要 5 分钟。
我相信复合应用程序是可行的方法 - 有人有什么想法吗？
I am developing an application out of two applications - the 'Staff DB' and a 'Calendar DB'.
I need to link both - so that clicking on a member of staff in the 'Staff DB' then looks up all their information in the 'Calendar DB'.
The link will be made by the UNID of the person, available in both databases and their respective forms.
If i was to write this in SQL it would take me about 5 minutes.
I believe composite applications are the way to go - does anyone have any ideas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
使用复合应用程序是可行的，因为您可以使用 UNID 将组件连接在一起。但您也可以使用“传统”Notes 设计来实现此目的。例如，您可以设计一个简单的表单，其中包含来自员工数据库的姓名列表和来自日历数据库的嵌入视图。嵌入视图可以配置为“显示单个类别”视图，该视图过滤内容以仅显示所选 UNID 的日历条目。 （构建视图时，添加 UNID 的第一个分类列）。设置名称列表字段以在更改时刷新文档。
如果这是一个纯 Web 应用程序，您还有其他选项，例如每当名称选择发生更改时，通过类别过滤器向视图 URL 发出 AJAX 请求等。
Using a composite application would work, as you could wire the components together using the UNID. But you could also do this using a "traditional" Notes design. For example, you could design a simple form with a list of names, sourced from the Staff DB, and an embedded view from the Calendar DB. The embedded view could be configured as a "show single category" view, which filters the content to only show calendar entries for the selected UNID. (When you build the view, add a first categorized column of UNID). Set the names list field to refresh the document when changed.
If this is a web-only app, you have other options as well, such as firing an AJAX request to a view URL with a category filter, whenever the name selection changes, etc.
根据我链接文档的经验，无论是在同一数据库还是在单独的数据库中，一个想法是捕获 UniversalID 并将其存储在文本项中，然后使用按该项排序的视图查找文档。
您获得的是管理链接的更大灵活性，因为您不依赖于无法更改的属性 (UniversalID)。不过，您会损失一些性能 - GetDocumentByUNID 应该是访问文档的最快方法之一。
One idea based on my experience linking documents, whether in the same or in separate databases, is to capture the UniversalID and store it in a text item and then look-up the documents using a view sorted by that item.
What you gain is more flexibility in managing the links, as you don't rely on a property (UniversalID) that you cannot change. You lose some performance though - GetDocumentByUNID is supposed to be one of the fastest ways to access a document.