5 ms·
Another issue is environments. It is generally a good idea to have a non-prod database agains which to test new queries and changes. This is impossible with fir
by noahtallen 7y ago
Another issue is environments. It is generally a good idea to have a non-prod database agains which to test new queries and changes. This is impossible with firebase/firestore without some hacks. In a previous job, we had two entirely separate firebase projects, one for dev and one for prod because it became untenable to test new database structure and changes against the prod DB.
- pier25 7y agoOh yes Jesus that's really bad too.
- databrecht 7y agoGood to know in that case, that you can create as many databases as you want in one FaunaDB account and even create databases in databases (parent keys get access to child databases) and probably won't get these issues. e.g. I run integration tests and create/destroy a child db for each test suite. Disclaimer: I'm a dev advocate there so I'm obviously biased