Do we have plan to implement a Relationship in table but different database?

As of now, the relationship should be table in same database. But does the appwrite team will have plan to have relationship in table but different databases?

What's the exact use case for this?

for example,

I create a user collection in my main database,

Now I have a another database called file system, so I have this attributes that indicates the owner of the file or folder, so I want to connect this attribute to my user collection in another database because I want to get the avatar of this user

I would expect not. I don’t think something like this would generally be possible with any database solution.

Why would you do this in a separate database, as opposed to a separate Collection?

I have multiple application

just imagine google products

if I have put it all in one database it hard to me locate the collection

so I have to refactor or encapsulate my collections

https://stackoverflow.com/questions/11426929/can-we-use-join-for-two-different-database-tables#:~:text=SQL%20Server%20allows%20you%20to,must%20fully%20qualify%20table%20names.

JOINs are not the same thing as Relationships

I do not think so on the backend process of Appwrite on how they managed the relationships

I'm not actually sure - will have to have a look at some point