Paul McCullagh wrote:
Hi Jay,
Let's assume for the moment that the BLOB implementation in MySQL was,
well, "as it should be".
Which would mean there are no adverse affects to storing BLOBs in a
table, the application can handle the large objects without any
special considerations, and the whole thing scales.
In other words:
- The programmer does not have to make special arrangements to handle
BLOBs.
- The DBA does not have to make special arrangements to get a
consistent backup or replicate the data.
If this was the case:
Would you change your mind about whether storing BLOBs in the database
is a bad design decision?
So I think Jim's point is this. Yes, putting a cow in a (normal)
fridge does not work.
But *not* because putting a cow in a fridge is a bad design idea. But
rather because the average fridge is not correctly designed for this.
On the other hand, ask a butcher and he will show his fridge which is
designed for this purpose, and explain the utility of it :)
I agree that Drizzle should focus core development elsewhere. But we
are many in the community... so we can do this as well. And the
additional functionality can be made pluggable.
Paul, we aren't going to win an argument with vegetarians for optimizing
storage for dead cows. Gotta find another analogy...
Jay, you set us up here, right?
--
Jim Starkey
President, NimbusDB, Inc.
978 526-1376
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
