4 ms·
As far as I'm aware these offerings support transactions across the entire database. Google Cloud Spanner: https://cloud.google.com/spanner/docs/transactions h
by airwot4 8y ago
As far as I'm aware these offerings support transactions across the entire database.
Google Cloud Spanner: https://cloud.google.com/spanner/docs/transactions https://cloud.google.com/spanner/docs/transactions
Google Cloud Firestore: https://firebase.google.com/docs/firestore/manage-data/transactions https://firebase.google.com/docs/firestore/manage-data/trans...
Plus if you use Cloud Firestore in Datastore Mode then Google Cloud Datastore would satisfy this requirement as well.
- otterley 8y agoSpanner is not a non-relational database. As for Firestore, it’s not clear whether it supports cross-collection transactions. Cloud Datastore does not support cross-namespace transactions AFAICT.
- wsh91 8y agoa) Cloud Firestore supports transactions across the entire database. You can learn more about them here: https://cloud.google.com/firestore/docs/manage-data/transactions https://cloud.google.com/firestore/docs/manage-data/transact.... b) Given that the primary use case for namespaces was/is multitenancy, it's not clear to me why you'd want to transact across them. Nevertheless, you can. What's leading you to draw this conclusion?
- otterley 8y agoThe documentation is what led me to that conclusion, since it's not explicit as to what the transaction boundaries are, but I could be mistaken. Does this mean that the poster's claim is erroneous?
- itcmcgrath 8y agoIt does. It's not in the documentation because it doesn't have boundaries within the database.
- otterley 8y agoCan you have more than one database per project? If so, there still might be a valid claim here.