Hi!
On Nov 10, 2008, at 7:27 AM, Jim Starkey wrote:
Philosophically, I'm not sure than inconvenience should be a major
consideration when considering architectures. If drizzle could
delay blob materialization to the last possible nanosecond in hope
it would need to, drizzle would be a great deal more application
friendly.
This is something I find more interesting because if we can delay the
last moment (or just pass in a fd/offset/length) we can do sendfile
tricks to just map from disk to card bypassing memory entirely. This
would mean though that an engine laid out a blob on disk as a single
object.
Part of he logic in the original protocol was:
SELECT a, b, c
Is that if I asked for the values in that order, I don't want to have
to make a second request for a particular member of that set. I have
already said "this is what I want, give it to me". The blob fetching
has always implied a sort of "but do you really want it?". The blob
fetching in Oracle was an original limitations of their design, it
just happened to be in MySQL that it didn't have that limitation
(though the current twice copy of blob data is ridiculous).
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
