3 ms·
It still uses a transaction log, but seems to make snapshots of the logs at a period of time to create compressed snapshots of the data itself. You can turn of
by chris_wot 14y ago
It still uses a transaction log, but seems to make snapshots of the logs at a period of time to create compressed snapshots of the data itself.
You can turn off durability, but then you risk losing everything.
For features... forget about geo-spatial extensions - they can only do read-committed isolation level... but as they only allow for one SQL statement per transaction I suppose this might not be such a big concern.
If you were using this for something like a session management database, or something where durability is not so important then it's probably fine. Not sure I'd use it for anything that relies heavily on transaction management features.
I see other limitations, like it cannot support CHANGE COLUMN, and it can't do joins on more than 2 tables. Actually, it doesn't look like it can do FULL OUTER or RIGHT OUTER joins, either. :(
- nikita 14y agoMemsql is a database that does some things incredibly well: deliver on high throughput for on small transactions and some things not as well (surface area). Of course a new product will have certain limitation which will be removed as the product matures.
- chris_wot 14y agoNo probs, like I've said elsewhere, not attacking the product. Looks very interesting! I guess I'm trying to work out what sort of market you are trying to target here.