We're currently not tracking at all whether or not a bundle has been checked out. Could do smarter things if we did.
Add a field to bundle.bundle called wc_commit_id, which is set based on whether or not a bundle has been checked out, and if so at what commit. Using this field, if a bundle has already been checked out and a user checks out a different version, checkout could intelligently delete any rows from the working copy that were deleted since the previously checked out commit. Also could prompt the user to checkout the bundle, if it's not checked out. And more. Big wins.
Instead how about a table bundle.checkout that logs checkouts, along with their commit_id, created_at, user_id and a note or message about who checked it out from what context, etc.
We're currently not tracking at all whether or not a bundle has been checked out. Could do smarter things if we did.
Add a field to
bundle.bundle
calledwc_commit_id
, which is set based on whether or not a bundle has been checked out, and if so at what commit. Using this field, if a bundle has already been checked out and a user checks out a different version, checkout could intelligently delete any rows from the working copy that were deleted since the previously checked out commit. Also could prompt the user to checkout the bundle, if it's not checked out. And more. Big wins.