No Data separation when using the Same Database

Let's consider a scenario where a singular database connection string is used across all data-partitions. If we create a new dataspace in any given partition, we observe that it is visible when we list dataspaces from other partitions. Hence, we can see all the dataspaces from every data-partition.

Is this an intentional design choice, suggesting that different databases should be utilized for different data-partitions?

Or, alternatively, would it be beneficial to add an additional column to our table(s), which would allow us to filter results by a data-partition identifier?