imagine: each new user results in a copy of the schema being installed in a new database with a unique password tied to the user's identity. they get their own databases and tables. and those tables in turn could be sharded. this way nobody would be able to see the user's data except them. but it also means we'd have to defer maintenance to their tables until the first time they login sincve we wouldn't have the key to unlock their database otherwise. what if there are CVEs whose fixes require changes to the code/tables. would w simply
would that quell any worries about data privacy? at hopefully not too crazy a cost? how would tings like flyway/liquibase work in this scenario?
imagine: each new user results in a copy of the schema being installed in a new database with a unique password tied to the user's identity. they get their own databases and tables. and those tables in turn could be sharded. this way nobody would be able to see the user's data except them. but it also means we'd have to defer maintenance to their tables until the first time they login sincve we wouldn't have the key to unlock their database otherwise. what if there are CVEs whose fixes require changes to the code/tables. would w simply
would that quell any worries about data privacy? at hopefully not too crazy a cost? how would tings like flyway/liquibase work in this scenario?