3 ms·
It's well suited to a certain class of applications, specifically web apps. I've never needed the things you list and I'm not the only one.
by azsromej 18y ago
It's well suited to a certain class of applications, specifically web apps. I've never needed the things you list and I'm not the only one.
- newt0311 18y agoI am sure that you are not the only one who requires such an application. Regardless, that is not a database (certainly not a relational/SQL one), it is effectively a dumb object store. I meant nothing derogatory when I pointed out that drizzle was not a database. Just that databases are a very well defined utilities (cf. ANSI SQL standard). MySQL already pushed the bottom end of the envelop. Calling drizzle a database is a flat out lie. Heck, if I ever just want a transactional system for storing undifferentiated blobs, I will probably end up using this product.
- henning 18y agoMore generally, there are basically two kinds of apps that connect to a database: "application databases" that are the primary or sole user of a database and use it for all their persistence needs, and "integration databases" that are one of many interacting with the database. Web apps usually work with application databases. AFAIK Martin Fowler coined this terminology/distinction, see http://martinfowler.com/bliki/ApplicationDatabase.html http://martinfowler.com/bliki/ApplicationDatabase.html . For application databases, usually having any kind of view/stored procs/triggers/prepared statements is a smell that you're conflating business logic with persistence.