YES YES YES -- +10 for this change. BUT ... I don't know if I'd worry
about synonyms. I think the important change is to move to the
DATABASE/SCOPE/COLLECTION model instead of the DATAVERSE/DATASET model.
We had one too few layers when we designed the "legacy" model. I would
like to see us essentially deprecate the legacy model and have the
three-level model be the new norm. (With some flag available for those
who want to work under the legacy model due to having existing data -
but hopefully there won't be a huge number of those.
If we do go the synonym route, I don't know if the 1:1 should be
SCOPE:DATAVERSE in a default DATABASE or if it should be
DATABASE:DATAVERSE with a default scope in between. (Both are messy,
which is why I'd be inclined to avoid the issue and not try to have them
play nicely together. The way that Couchbase handled the 2-part vs.
3-part world stitching when they moved to the 3-level model wasn't ideal
- it's kind of the gift that has kept on giving... :-)
Cheers,
Mike
On 5/12/26 9:27 AM, Ian Maxon wrote:
Hi all,
I wanted to start a discussion regarding the idea of making DATABASE
the default top-level entity for the next release. Currently it's only
enabled if you have a cloud deployment. However in various informal
conversations among various PMC members and Committers, the idea has
come up many times that it's a good idea and should be the new
default, regardless of deployment mode.
Another related topic would be making SCOPE a synonym to DATAVERSE. I
was playing around with things currently and basically the way things
are today, COLLECTION is a synonym to DATASET but DATAVERSE has no
synonym, at least it seems.
What does everyone think?
- Ian
