Skip to content

Document loadRegistry() behavior for exported objects #334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jemus42 merged 1 commit into from
Oct 1, 2026
Merged

Document loadRegistry() behavior for exported objects #334

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions R/loadRegistry.R
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,10 @@
#' @description
#' Loads a registry from its \code{file.dir}.
#'
#' Objects previously exported with \code{\link{batchExport}} are automatically
#' loaded into the global environment when the registry is loaded. Existing
#' objects with the same names may be overwritten.
#'
#' Multiple R sessions accessing the same registry simultaneously can lead to database inconsistencies.
#' This is especially dangerous if the same \code{file.dir} is accessed from multiple machines, e.g. via a mount.
#'
Expand Down
Loading