Jump to: navigation, search

Difference between revisions of "Trove/DatastoreCompatibilityMatrix"

(Extensions Matrix)
(Extensions Matrix)
Line 94: Line 94:
 
| style="color: red" | ✗         
 
| style="color: red" | ✗         
 
| style="color: red" | ✗             
 
| style="color: red" | ✗             
 +
| ✔       
 
| style="color: red" | ✗             
 
| style="color: red" | ✗             
| ✔       
 
 
|-
 
|-
 
| Schemas                     
 
| Schemas                     
Line 102: Line 102:
 
| style="color: red" | ✗             
 
| style="color: red" | ✗             
 
| style="color: red" | ✗           
 
| style="color: red" | ✗           
 +
| ✔*       
 
| style="color: red" | ✗           
 
| style="color: red" | ✗           
| ✔*       
 
 
|-
 
|-
 
| Root                 
 
| Root                 
Line 110: Line 110:
 
| style="color: red" | ✗           
 
| style="color: red" | ✗           
 
| style="color: red" | ✗   
 
| style="color: red" | ✗   
| style="color: red" | ✗         
 
 
| ✔**         
 
| ✔**         
 +
| style="color: red" | ✗       
 
|-
 
|-
 
|}
 
|}

Revision as of 14:33, 19 September 2014

This page will detail which datastores have which functions, either core or extension form.

API Matrix

Feature MySQL Redis Cassandra MongoDB PostgreSQL Couchbase
Launch
Reboot
Terminate
Resize
Backup
Restore
Replication - - - -
Clustering - -

Extensions Matrix

This covers items that are not considered part of the core api (yet). As more datastores start to use extensions, we can move them to core.

Feature MySQL Redis Cassandra MongoDB PostgreSQL Couchbase
Users
Schemas ✔*
Root ✔**

* PostgreSQL supports has separate constructs for schemas and databases.

** PostgreSQL supports superusers but does not have a "root" user.